The Dial Next to the Meter: Stretching Claude Fable 5 Credits with Effort Levels

This morning’s post was about the meter: Sol at half Fable’s price, the reset that followed OpenAI’s rollout tweet by thirty-one minutes, the meter starting Monday. This one is about the dial sitting next to it. The day before the GPT-5.6 launch, Anthropic’s Claude Code team published an explainer on model selection and effort levels, and buried in it is the most useful cost lever most Claude users have never deliberately touched.

Everyone Reads the Dial Wrong

The common mental model is that effort means thinking time: turn it up and Claude ponders longer before answering. The article is blunt that this is wrong. Effort controls how much total work Claude does on your request:

• How many files it reads before acting
• How much it verifies: running tests, double-checking its own output, revisiting hypotheses it could have skipped
• How far it pushes through a multi-step task before checking in with you

At low effort, Claude would rather ask you a question than spend tokens figuring something out on its own. The article’s illustration puts the same prompt at roughly 7x more tokens on the high-effort path. Thinking, tool calls, and text to you are all output tokens from the same loop, billed at the same rate, so that multiplier is your bill.

The Meter Makes It a Price Control

While Fable 5 was free-in-subscription, effort was a latency preference. From Monday it draws metered credits at $10 / $50 per million tokens, counting roughly double Opus against plan limits. A dial that swings token consumption several-fold on the same task stops being a preference and becomes the price control you actually own. OpenAI monetizes the same idea in the opposite direction: Sol’s ultra mode spends four parallel agents’ worth of tokens to buy a better answer. Anthropic’s dial turns down; OpenAI’s turns up. Both companies now sell thoroughness by the token.

The Fable Inversion

The load-bearing fact is in Anthropic’s migration docs, not the article: lower effort settings on Fable 5 still perform very well, often exceeding the xhigh or even max performance of previous models. The capability floor moved up far enough that the bottom of Fable’s dial sits above the top of Opus 4.7’s.

Fable is the specialist you call when everyone else is stuck.

— Anthropic, on model selection in Claude Code

The article’s version of this is the specialist’s five minutes: even at low effort, Fable spots the thing no one else would. That recognition is what you’re paying for, and it survives the dial. What doesn’t survive is the careful pass through every file.

What You’re Actually Turning Off

Here’s the trade nobody prices in. Opus 4.8’s headline feature was honesty: self-verification you’d otherwise do by hand, paid for in tokens. Effort is the knob on exactly that behavior. At high effort Fable checks its own work before showing you; at low effort it hands you unverified output and a question. The tokens you save are the verification you just agreed to do yourself.

That makes the dial task-shaped:

• Low effort earns its keep on review, architecture judgment, “what’s wrong here” questions: things where you’re the verifier anyway and Fable’s pattern recognition is the product.
• Low effort backfires on long autonomous builds, where one unverified wrong turn costs more tokens to unwind than the checking would have. On genuinely hard multi-step work, Anthropic’s own curves show the equation flipping: a capable model at normal effort finishes in fewer iterations than a constrained one grinding at its limit.

Plan Big, Execute Small

For agentic work there’s a better credit-stretcher than throttling the specialist. Two days ago Anthropic published numbers for a Fable 5 orchestrator delegating to Sonnet 5 worker subagents: 96% of Fable’s performance at 46% of the price on BrowseComp. Fable keeps the judgment, Sonnet does the token-heavy grunt work. In Claude Code terms: main loop on Fable at default effort, subagents on Sonnet. You stop paying specialist rates for file-grepping without giving up the specialist.

Long-time readers will recognize the shape. Planning with the biggest model you can afford has been the advice here since Plan Mode went mandatory in 2025, and Claude Code was quietly built as a multi-agent system with cheap hands months before agent teams shipped. What’s new isn’t the pattern. It’s that Anthropic now publishes the price tag on it.

The self-inflicted usage squeeze I wrote about last week (one session burning 14M tokens across 451 subagents) is the same lesson from the other side. The orchestrator pattern isn’t about spawning less; it’s about spawning cheaper.

What the Dial Doesn’t Solve

• Effort shapes consumption but doesn’t cap it. A task that needs the work still burns. The only hard ceiling is max_tokens, which truncates mid-stream; task budgets are the softer control the model actually paces itself against.
• Toggling mid-session costs you the cache. Users on r/ClaudeAI discovered this week that changing the effort level invalidates the prompt cache, so a mid-session flip pays a full-history cache rewrite at premium write rates. Set effort per session, not per message.
• Your time is a cost too. Low-effort Fable asks more questions. If each clarifying round-trip costs you five minutes of attention, the token saving can be the expensive option.

The morning story was two companies fighting over who bills less per token. The afternoon story is that your bill was never really about the per-token price. It’s about how many tokens you ask for without noticing, and the dial that decides that has been sitting in the settings the whole time.