Opus 5 wins the benchmarks. Why are veterans switching back to Fable 5?

On July 24, 2026, Anthropic shipped Claude Opus 5 with a benchmark table that is hard to argue with. Within 48 hours, several developers whose judgment a lot of us have relied on for years said they had tried it and gone back to Fable 5.

Both things are on the public record. The interesting question is not which side is right — it is what the gap between them tells you about how to choose a model now.

What the benchmarks say

Anthropic's published figures, verified as of July 27, 2026:

• Frontier-Bench v0.1: Opus 5 at 43.3%, Fable 5 at 33.7%, Opus 4.8 at 18.7%.
• CursorBench 3.2: at max effort, Opus 5 lands within 0.5% of Fable 5's peak, at roughly half the cost per task.
• ARC-AGI 3: about three times the score of the next-best model.
• Zapier AutomationBench: at the same cost per task, a pass rate around 1.5x the next-best model.
• OSWorld 2.0: exceeds Fable 5's best computer-use result at slightly more than a third of the cost.

Artificial Analysis puts Opus 5 at 61 on its intelligence index against Fable 5's 60 at max effort, with cost per task of roughly $2.03 against $2.75.

Add the list price — $5/$25 per million tokens against Fable 5's $10/$50 — and there is no reading of the published record in which Opus 5 loses. On paper it is the same capability band at half the price, without Fable 5's mandatory 30-day data retention.

A mini-bench you can re-run

The gap between the chart and the timeline is a dispute about task quality, and the cheapest way to get a second opinion is to write a few small, reproducible tasks and run both models at matched effort. Below are four we ran ourselves on July 28, 2026, on a throwaway repository. They are illustrative, not a controlled study — single runs, no statistical power, and nothing frozen beyond the model ID. Treat each row as a starting point to re-run, not as a verdict. Figures are approximate and dated as of July 28, 2026.

Refactor a 300-line component into a hook + reducer. Both models landed a working split on the first pass. Fable 5: pass, ~9.4k in / 2.1k out tokens, ~$0.20. Opus 5: pass, ~9.1k in / 1.8k out, ~$0.09.

Debug a flaky test that passes locally but fails in CI. Fable 5 found a missed await in a mocked fetch and a non-deterministic sort order in 3 turns ($0.40). Opus 5 found the same two in 2 turns, with fewer re-reads ($0.16). Both were correct on the run we scored; not confirmed that a different seed reproduces either.

Multi-file change: add an endpoint, wire it to a client hook, add a test. Fable 5 landed the change in one pass, but its test copied an existing fixture rather than asserting the new field ($0.27). Opus 5 landed the change and asserted the field ($0.12).

Repo-analysis question on a small monorepo. "Where does the failed-webhook retry actually live, and is it covered?" Fable 5 mapped it correctly in 2 turns ($0.16). Opus 5 gave the same answer in 1 turn, on roughly a third fewer input tokens ($0.06).

What our four rows showed. Both models went 4/4 on pass/fail and were cheap; on task quality they were effectively tied. The measurable difference was Opus 5's token efficiency — roughly $0.43 against $1.03 for the same sweep — which is exactly the variable the critical threads skip. A tie on four tasks is not a tie on your work. Re-run it before you trust it.

How to re-run. Freeze everything except the model ID — same prompt, same repository state, same effort tier, same retry policy. One run per model per task; record solved or not, turns, input and output tokens separately, and wall-clock time. Rank on cost per solved task rather than pass rate. At $5/$25 per million tokens the whole sweep runs to about a dollar. Do not generalize from a single run — including this one.

What the practitioners said

What follows are public statements by individuals about their own work. None of them report a task set, a methodology, or an effort level, and all were made within three days of launch. Read them as signal, not as evidence.

Jeremy Howard tested Opus 5 and switched back to Fable 5, describing the newer model as a regression on his tasks.

Kun Chenguid, in a critique amplified by Peter Yang, wrote: "opus 5 is nowhere near fable in practical use, not even close. anyone who's used it meaningfully can tell this very quickly after a few tasks. yet opus beats fable on many benchmarks." The same thread went further than the model comparison, arguing that today's popular public benchmarks have stopped being informative and that domain-specific evals built on private data are the ones worth trusting.

The developer @badlogicgames also said he had switched back to Fable.

Yam Peleg amplified the thread, which is how most people encountered it. The roundup is at digg.com/tech/2jlmpohd, retrieved July 27, 2026.

Notice what is not being claimed. Nobody in that group published a pass/fail count. "It felt worse on my work," from someone with a long track record, is worth hearing — and it is also precisely the kind of claim that survives contact with reality whether or not it generalizes.

The counterpoint

It was not unanimous. On r/ClaudeAI, /u/Meme_Theory posted on July 25, 2026 under the title "Opus 5 Token Usage is Amazing," reporting that work which had eaten a substantial share of a Max x20 allowance on Fable 5 barely moved the counter on Opus 5, with results they were happy with.

That is an anecdote with the same methodological weight as the ones above, which is to say some. But it points at a variable the critical reports mostly skip: what the answer cost, not just whether it was good. If Opus 5 reaches a slightly worse answer using half the tokens at half the price, "worse" and "better" stop being the right words.

Four reasons scores and feel can diverge

These are hypotheses, not findings. Nobody has isolated the cause, and it is entirely possible that the critics are simply right.

The charts are run at the top of the ladder. Anthropic's headline CursorBench and Frontier-Bench results were produced at max effort. Low, medium and high are the tiers most people actually run, and xhigh and max are API-only. If you switched models and kept your defaults, you did not deploy the model in the chart.

Prompts carry forward; behaviour does not. A harness tuned over weeks against Fable 5 encodes assumptions about how that model plans, when it stops, and how much it reads before acting. Swapping the model ID keeps the scaffolding and changes the thing it was shaped around. The first week after any model launch is measuring the mismatch as much as the model.

Benchmarks score the destination; you feel the path. A benchmark records whether the final diff passes. Sitting next to an agent, you notice the detours, the re-reads, the confident wrong turn on step four. Two models can converge on the same pass rate and be very different to work with.

Launch-week reports select themselves. People post when a new model surprises them, in either direction. The developers who swapped one line and kept shipping had no reason to write a thread about it. A count of loud opinions is not a sample.

Settle it on your own tasks

The honest conclusion from the last few days is that public benchmarks and public sentiment now disagree often enough that neither is a substitute for a local measurement. The good news is that a local measurement is cheap.

1. Pull 10 to 20 tasks from your own history. Closed tickets, merged pull requests, real support threads — work where you already know what a correct outcome looks like. Synthetic prompts will reproduce whatever bias you brought to writing them.
2. Freeze everything except the model ID. Same system prompt, same tools, same repository state, same retry policy. If you tune the prompt for one model, tune it for both or you are measuring your tuning.
3. Match the effort level deliberately, then vary it. Run both models at the tier you would actually ship, record the result, then run Opus 5 one tier higher. The cost difference may still leave you ahead.
4. Record four numbers per run: solved or not, turns taken, input and output tokens separately, and wall-clock time. Write them down before you form an opinion about the transcript — reading the reasoning first will colour the grade.
5. Rank on cost per solved task. Pass rate alone hides retries; token count alone hides failures. One avoided rerun moves the arithmetic more than any single benchmark point.
6. Re-run when either model ships an update. Both are weeks old. Anything you conclude today has a short shelf life, and that includes this article.

At $5/$25 per million tokens, a twenty-task sweep across two models usually costs a few dollars. That is a smaller budget than the time already spent reading arguments about it.

What is not in dispute

While the quality question stays open, a few decision-relevant facts do not:

• Opus 5 lists at $5/$25 per million tokens against Fable 5's $10/$50, with cache reads at $0.50 and batch at $2.50/$12.50.
• Opus 5 carries no data retention requirement for general access. Fable 5 requires 30 days and is excluded from zero-data-retention agreements. If a compliance review blocked Fable 5 at your company, that blocker is gone.
• Opus 5 is the default model on Claude Max and the strongest model on Claude Pro, at unchanged subscription pricing.
• Fable 5 left Pro and Team Standard on July 20, 2026, replaced by a one-time $100 credit. On Max and Team Premium it remains included up to 50% of the weekly allowance.

For a lot of teams, the retention line settles the question before the benchmark table gets a vote.

Where that leaves you

If you are starting something new, Opus 5 is the reasonable default: same capability band on every public measurement, half the price, fewer contractual complications. If you have a tuned Fable 5 harness that is producing good work at an acceptable cost, the case for touching it this week is weak — and the people saying so out loud are not the kind of people who are usually wrong.

What you should not do is let either the benchmark table or the timeline make the call. Both are cheaper to acquire than a real measurement, and both are worth correspondingly less.

For the specification and pricing differences side by side, see Claude Fable 5 vs Claude Opus 5. To put your own monthly volume through both price points before you commit, use the cost calculator.

Benchmark and pricing figures from Anthropic's published materials and Artificial Analysis, verified July 27, 2026. Community statements retrieved July 27, 2026 from digg.com/tech/2jlmpohd and r/ClaudeAI. Independent analysis — not affiliated with Anthropic.