Why effort matters more on Fable than anywhere else
On Fable 5, effort is the primary dial trading intelligence against latency and cost. Other prompting choices nudge the model; effort decides what kind of worker shows up. Anthropic's prompting playbook treats it as the first decision you make for any task — before the prompt, before the tools.
The four settings
Quick questions, rewrites, interactive back-and-forth where every extra second of thinking is a second you're waiting. Don't read "low" as weak: low effort on Fable often beats maximum effort on prior models.
Routine work with a little substance — ordinary edits, short analyses, everyday coding turns. The same caveat applies: still strong, and fast enough to stay conversational.
The recommended default. Real engineering, real writing, real analysis — the setting Anthropic suggests you start from and adjust away from only with a reason.
Capability-critical work where quality is non-negotiable: the hardest debugging, tasks where one wrong answer costs more than the tokens, long autonomous runs nobody will be supervising. This is where Fable's best verification and reasoning behavior lives.
The two failure modes
Fable will happily over-deliberate a simple job — longer waits, wasted tokens, no better answer. The tell: a task completes correctly but takes too long. That's your signal to reduce effort, not to rewrite the prompt.
Higher effort also brings the model's best verification and reasoning behavior — the double-checking that catches its own mistakes. Starving your hardest jobs to save latency buys you a fast wrong answer. If quality is the point, pay for the thinking.
The effort picker
| Task type | Suggested effort |
|---|---|
| Quick questions, chat, interactive back-and-forth | low |
| Routine edits, rewrites, everyday coding turns | low / medium |
| Serious engineering, analysis, substantial writing | high (the default) |
| Whole-codebase review, hardest debugging | xhigh |
| Long autonomous runs, unsupervised builds | xhigh |
| Anything where one wrong answer costs more than the tokens | xhigh |
Two practical notes
- Long runs are normal. Hard tasks at higher effort run for many minutes in a single request. That's the design, not a hang — adjust your client timeouts and go do something else; don't stare at spinners.
- Steer with one sentence, not a rulebook. On Fable, one brief instruction changes behavior more reliably than the long rule lists you wrote for older models — over-specified prompts can actually degrade output. The full playbook translation, with Anthropic's copy-ready instructions, is Recipe 07.
Effort answers how hard Fable should work; it doesn't answer whether the job belongs on Fable at all. For that triage — what earns Fable's rate and what a cheaper model does just as well — see what to run on Fable 5.
Moral: match the effort to the stakes, not to the model's reputation — Fable at low effort is still Fable, and Fable at xhigh is only worth it when being wrong is expensive.