Fable 5 vs Opus 4.8 — upgrade or wait?
Same company, same API, one costs exactly twice as much — and the cheaper one is wired into the expensive one as its safety net. That's the decision Anthropic handed every operator on June 9, 2026, with a plan window that closes June 22 (the API meters from request one). Here's the file.
Numbers from Anthropic's announcement and the model's API surface. The full model file lives on the Fable 5 hub; the benchmark caveats on the benchmarks page.
Jump to section tap to open
The 30-second answer
Long-horizon agentic work → Fable 5: SWE-Bench Pro 80.3% vs 69.2%, FrontierCode 29.3% vs 13.4%. Cyber/bio-adjacent or cost-sensitive bulk → stay on Opus 4.8 — it is not deprecated, and in the Claude apps Fable falls back to it anyway (on the API a blocked request errors, unbilled). Decide on your own eval before June 22, while Fable sits inside plan limits.
The decision table
| What you're weighing | Fable 5 | Opus 4.8 |
|---|---|---|
| API price (per Mtok) | $10 in / $50 out | $5 in / $25 out — exactly half |
| Context window | 1M tokens | 1M tokens |
| Max output | 128K | 128K |
| API surface | Same as Opus 4.7/4.8, plus one new 400: explicit thinking: disabled rejected | Adaptive thinking only; explicit disable accepted |
| SWE-Bench Pro (agentic coding) | 80.3% | 69.2% |
| FrontierCode (Diamond), xhigh | 29.3% | 13.4% |
| GDPval-AA (knowledge work) | 1932 | 1890 |
| OSWorld-Verified (computer use) | 85.0% | 83.4% |
| Fallback when a classifier trips | apps/CMA → Opus 4.8 (you're told); API → unbilled error, opt-in fallback at Opus pricing | is the fallback target |
One more operational difference that doesn't fit a row: the minimum cacheable prompt prefix drops from 4096 tokens on Opus 4.8 to 2048 on Fable 5. Details on the API page; full pricing math on the pricing page.
Read the table cold and the pattern is plain: the spec sheet is nearly identical, the price doubles, and the gap lives in two places — agentic coding and the fallback row. Everything below is about whether those two places are where your work lives.
Where Fable 5 wins — the long horizon
The headline isn't the eleven points on SWE-Bench Pro. It's FrontierCode (Diamond) at xhigh: 29.3% vs 13.4% — a 2.2× gap on the eval built to resist saturation. Gaps that size don't appear from contamination; they appear when a model holds a plan across more steps before it loses the thread.
The launch receipts say the same thing — and they're vendor-curated, so hold them at arm's length. Stripe: a 50-million-line Ruby codebase migration done in one day that was scoped at two months by hand. GitHub: long-horizon coding tasks handled with "a level of autonomy and reliability that exceeded previous benchmarks." Cursor: "state of the art model on CursorBench." Three different shops, one claim — fewer turns on longer work.
That's the only claim that justifies a 2× sticker. A model that finishes in one pass at $10/$50 beats one that needs five retries at $5/$25 — on the bill and on your time reading wrong answers. Whether Fable 5 does that on your repo is exactly what the free window exists to answer.
Where Opus 4.8 stays right — no strawman
Cyber- and bio-adjacent work. Fable 5 ships with blocking classifiers in front of offensive cyber and biology/chemistry, and Anthropic's own footnote says the starred benchmark rows show Fable performing closer to Opus 4.8 there because of fallbacks — by design. Paying $10/$50 to behave like the $5/$25 model is not an upgrade, it's a markup.
Knowledge work. GDPval-AA reads 1932 vs 1890 — 42 points. If your workload is documents, analysis, and drafting rather than multi-hour agent runs, the launch table itself says the gap is thin. A 2× sticker needs more than thin.
Cost-sensitive bulk. Classification, extraction, pipeline drafting — the routing logic from Ch 29 didn't change on June 9. Opus 4.8 at $5/$25 keeps the heavy-but-routine lane, and the Sonnet/Haiku tiers below it keep the bulk lane. The tier list stays the live source of truth.
The irony — Fable's safety net is Opus 4.8
Sit with the architecture for a second. Three classifier areas guard Fable 5 — offensive cyber, biology/chemistry, capability distillation. When one trips in the Claude apps or Managed Agents, your response is generated by Opus 4.8 and you're told. On the Messages API a blocked request returns an error, unbilled — fallback to Opus 4.8 is opt-in, billed at Opus pricing. Anthropic states more than 95% of Fable sessions involve no fallback at all.
Which means for safeguarded domains, this comparison answers itself. Ask Fable 5 a question in a guarded area and — in the apps — Opus 4.8 answers anyway: the frontier delta you upgraded for vanishes mid-task. On the API the request errors instead. If your work is security tooling, exploit research adjacency, or anything bio-flavored, don't run the experiment: route to Opus 4.8 directly and skip the detour. For everyone else, the 95% number says the classifiers are something you read about once and never meet.
The move — what I'd do before June 22
- 1 — Use the window. Fable 5 is inside paid-plan limits June 9–22, 2026. That's a two-week free private-eval window on frontier capacity. Point it at the workloads where Opus 4.8 makes you retry, and keep the transcripts.
- 2 — Swap one string, not your stack. If your model id lives in config, the trial is a one-line diff:
claude-fable-5. Same API surface as Opus 4.8 with one new 400 — explicitthinking: disabledis rejected, so omit the param. The rest is on the API page. - 3 — Measure cost per finished task. Not per token. Ch 29's math is the whole decision: if Fable 5 collapses your turn count, 2× the rate is a discount; if it doesn't, it's just 2× the rate.
- 4 — Don't re-route on a launch table. The book's standing discount on public scores — the Berkeley-RDI receipt in research notes (eight major agent benchmarks reward-hacked in April), run through Ch 25's discipline — is 10–15 points. The table above is a signal. Your eval is the receipt.
No five-lessons wrap. The launch table opens the question; only your workload closes it — and closing it costs nothing until June 22.
FAQ
Is Fable 5 worth 2x the price of Opus 4.8?
For long-horizon agentic work, the launch evidence says yes: SWE-Bench Pro 80.3% vs 69.2%, FrontierCode (Diamond) 29.3% vs 13.4%, and Stripe's vendor-cited receipt of a 50-million-line Ruby migration in one day vs two months by hand. But those are first-party numbers. The honest answer: Fable 5 is inside paid-plan limits June 9-22, 2026 — run your own workload in that window and decide on cost per finished task, not dollars per token.
Is Opus 4.8 deprecated now?
No. Opus 4.8 remains current and supported at $5/$25 per million tokens. It is also load-bearing inside Fable 5 itself: in the Claude apps and Managed Agents, when a Fable classifier trips (cyber, bio/chem, or distillation), the response comes from Opus 4.8 — and you are told. On the Messages API a blocked request returns an error, unbilled; fallback to Opus 4.8 is opt-in, billed at Opus pricing. A model cannot be deprecated and be the safety net at the same time.
Can I use both Fable 5 and Opus 4.8?
Yes — and you should. The API surface is the same — adaptive thinking only, no temperature/top_p/top_k, no last-assistant-turn prefills — so routing between claude-fable-5 and Opus 4.8 is a model-id string per workload. One gotcha when switching: an explicit thinking type of "disabled" returns a 400 on Fable 5 (Opus 4.8 accepts it) — omit the thinking parameter instead.
Which is better for coding — Fable 5 or Opus 4.8?
Fable 5, on every reported coding benchmark: SWE-Bench Pro 80.3% vs 69.2%, FrontierCode (Diamond) at xhigh 29.3% vs 13.4%, Terminal-Bench 2.1 88.0% vs 82.7%. Apply this book's standing 10-15-point discount on public scores and the shape still holds — but a benchmark is a signal, not a receipt. Confirm on your repo before June 22.
Which model does Claude Code use by default?
Anthropic does not state a default switch in the announcement, so I will not invent one. What is verifiable: the Claude Code banner offers Fable 5 as "our newest model for complex, long-running work," included in plan limits until June 22, and you pick your model via /model. Opus 4.8 remains available there too.
The Fable 5 files
One model, two names — the safeguards, the fallback, the gated twin.
Benchmarks, read honestlyAll thirteen benchmarks, the starred-row caveat, and the reward-hacking discount.
Upgrade or wait — the 2× sticker against the turn-count collapse.
The cross-vendor read, including where the rivals' CLIs hold up.
Pricing + cost per task$10/$50, the plan window, and the Ch 29 math on 2× stickers.
Use casesStripe's 50M-line day, Cursor, GitHub, trading desks, drug design — and the operator's own.
Fable 5 in Claude CodeThe banner, the June 22 clock, /model, and when to route to it.
The API pageclaude-fable-5, the one new 400, and the one-line migration from Opus 4.8.
Related: The Fable 5 hub · Ch 24 — the tier list · Ch 29 — cost economics · Ch 2 — the five-tool stack · The live tier list