Claude Fable 5.2: the price cut is the story

Anthropic released Claude Fable 5.2 and Claude Mythos 5.2 today. Both beat Opus 5.5 on almost every capability they evaluated. The benchmark wins are the headline. The price cut is the part that changes how you use them.

Prices

Fable 5.2 and Mythos 5.2 cost the same:

Both are cheaper than the 5.1 versions. The page does not list the old numbers, so I will not guess them.

What the new prices buy, in plain arithmetic. A run that reads 1M tokens and writes 200k costs $8 + $8 = $16. The same run at Fast mode prices costs $32.

Benchmarks

On Anthropic’s own evals, Fable 5.2 beats Opus 5.5:

Fable 5.269.9Opus 5.562.3

Fable 5.249.1Opus 5.545.5

The number I care about is not in a table: at High effort, Fable 5.2 lands roughly on par with Opus 5.5 at Max effort on FrontierCode 2.0, at about half the cost per task. Max effort is the setting that spends the most tokens per answer. Getting the same result from a cheaper setting is where the savings live.

Output is up to 30% faster than Fable 5.1 and Mythos 5.1. Both models take a 1M token context and write up to 128k tokens per response.

The demos

Two demos from the announcement, because they show what the model is aimed at:

• Starting from an empty folder, the model coordinated over 1,000 subagents, working around the clock for eight days, and produced a working prototype operating system. It boots on a laptop, with its own kernel, drivers for disk, keyboard and network, persistent file storage, windows, a login screen, an installer, and built-in Claude functionality.
• It formalized Fermat’s Last Theorem in Lean in under 30 hours, a first.

Both are prototypes, not products. The signal is the shape of the work: long, parallel, self-reviewing runs with many agents under one coordinator.

What this means for my daily driver

I run Opus 5.5 through Claude Code all day. My tracker shows the last 30 days at $1,199.57: 11.9M output tokens, 3.18B cache reads. Cache reads are the bulk of the volume, which is why the output price matters more than it looks: every token the model writes is the expensive part.

Anthropic still recommends Opus 5.5 as the daily driver and Fable for the large tasks. The company’s own guidance, and the one I agree with: most requests do not need the biggest model, and the effort settings matter more than the model choice. At High effort Fable 5.2 is about twice as fast as the default and still beats Opus 5.5 Max on the coding eval above.

Two patterns from the post are worth copying regardless of which model you pay for. The advisor pattern: Fable 5.2 plans, a smaller model executes. The orchestrator pattern: Fable 5.2 coordinates a team of subagents and decides when the work is done. Both buy speed or quality with architecture instead of with a bigger single bill.

What I didn’t test

• I have not run Fable 5.2 myself yet. Every number here comes from the official announcement, fetched today.
• Cache pricing for the new models is not published, so I cannot recompute my own bill at the new rates yet.
• No long-context runs, no effort-level sweeps, no independent evals.

Once I can run it through my own stack, I will publish the measured version of this post, same as I did with the DSpine numbers.