Claude app tutorial
How to Use Claude Fable 5.2 in Claude
If your Claude account opens a different model by default, Fable availability can be easy to misread. We used the Claude Help Center's model and launch-offer guidance for these steps. The sample brief is for a fictional business so you can try the workflow with your own approved facts.
The quick steps
Check Settings → Usage, open a new conversation, select Fable 5.2, then send one tightly scoped task. Review the output against your source packet and hand off only the verified brief.
1. Check the plan and allowance
Open Settings → Usage in Claude and look for Fable access and usage credits on the selected account or team. Anthropic listed a launch allowance for Pro and standard Team seats through November 16, 2026 at 11:59 p.m. Pacific time, up to half of weekly usage limits. Usage credits can apply after the allowance if enabled. Use the live Usage screen and help page for the rules that apply to your seat.
2. Choose Fable 5.2 in a new chat
Open the model picker in Claude on web, Desktop or Mobile and select Fable 5.2. Confirm the selected name before submitting. If it is missing, first check that you are in the intended organization and that the selected seat has the required allowance or credit access. Claude Code and the API have separate access paths.
3. Send one brief request
For fictional Fern Dock Coffee, supply the approved Friday tasting schedule, one photo and the booking link. Give the model one job and one output shape so you can check whether it carried the facts through correctly.
Use only the attached photo and approved facts below. Write a brief for one square café tasting graphic. Return audience, exact offer text, one visual direction, booking call to action and unknowns. Quote any source that supports an offer claim. Keep unconfirmed details out of the final copy.4. Verify the brief against the source
Check the exact date, time and booking action first. Ask where the model got any new claim, such as the number of available seats. Move unconfirmed details to the unknowns field and ask the event owner before using them.
5. Hand the approved brief to your design tool
Place the image and exact approved copy on a Ciyo canvas. Paste the creative direction into the Design agent and keep the approved facts visible for comparison. Check the visual's lettering and crop before using it.
Keep account access separate from the creative task
If the model is missing, first confirm the account and workspace shown in Claude. On a managed team, ask the workspace owner whether the model is enabled for your role. Avoid changing the brief repeatedly while the underlying problem is access.
Once the model is available, keep the Fern Dock request small: one event, one approved offer and one booking action. A finished text brief is the handoff. The later Ciyo visual is a separate step and should be checked against those same facts before it is shared.
Frequently asked questions
Does the launch offer change my default model?
Anthropic says the default stays the same. Select Fable 5.2 explicitly in the picker.
Do I need an API key for the Claude app?
The app uses your Claude account. The separate API quickstart uses Claude Platform authentication.
Start from the approved facts
Use one photo and the accepted brief to start the café graphic on a Ciyo canvas.