Fable 5.1 beats Fable 5. Opus is harder to replace

Anthropic released Claude Fable 5.1 on September 1, 2026. It is a real upgrade over Fable 5, especially on long agent work, but not a clean replacement for Opus 5. Independent results put Fable 5.1 slightly ahead or tied with Opus, while its base input and output rates cost twice as much. [1] [7] [9] [19]

What changed in Fable 5.1?

Fable 5.1 keeps the same context window, output limit, and base API price as Fable 5. Opus 5 has the same limits at half the base input and output rates. The meaningful changes are better long-horizon performance, cheaper cache reads, a newer knowledge cutoff, and several API rules that make migration more than a model-ID swap. [2] [4] [5]

Anthropic calls the predecessor Claude Fable 5, not Fable 5.0, so I use the official name here. [4]

Specification	Fable 5.1	Fable 5	Opus 5
Context window	1M	1M	1M
Maximum output	128K	128K	128K
Input, $/MTok	10	10	5 (Best value in this row)
Output, $/MTok	50	50	25 (Best value in this row)
Cache read, $/MTok	0.25 (Best value in this row)	1.00	0.50
Default effort	high	high	high
Knowledge cutoff	Jun 2026	Jan 2026	May 2026

Figure 1 shows why Anthropic’s own recommendation matters. The company calls Fable 5.1 its most capable generally available model, yet tells developers to start with Opus 5 for most workloads and move to Fable only when Opus at higher effort still falls short. [2] Fable is the escalation path, not the default hidden behind a larger number.

The pricing change is narrower than the launch language can make it sound. Fable 5.1 still costs $10 per million input tokens and $50 per million output tokens, exactly like Fable 5. Its cache-read rate falls by 75%, from $1 to $0.25. Anthropic estimates that its August workload mix would cost about 25% less, with savings approaching 45% for heavily cached agent work, but that estimate depends on reuse and task behavior. [1] A request that reads fresh context once and writes a long answer gets no 75% discount on its main charges.

The product also changed in ways the table cannot show. Fable 5.1 can vary effort by message, accept turn-specific system instructions, and send visible progress updates between tool calls. Anthropic also documents denser prose, less predictable parallel tool use, and a tendency to rewrite whole files rather than make small edits. [6] Those are not side notes for coding agents. They change how a good score feels while someone is waiting, reviewing, or trying to stop a run.

Does Fable 5.1 beat Fable 5 and Opus 5?

Fable 5.1 clearly beats Fable 5 across the strongest matched agent evaluations I found. It does not clearly separate from Opus 5. The gap over Opus ranges from large on one Anthropic-run science benchmark to effectively tied on independent software and professional-work tests.

Evaluation	Fable 5.1	Fable 5	Opus 5
Terminal-Bench-Science 0.1, %	52.6 (Best value in this row)	24.7	29.0
CursorBench 3.2 max, %	73.4	70.5	70.0
GDPval-AA v2, Elo	1,853	1,723	1,824
APEX-SWE max, %	63.6	58.8	63.7
FrontierCode Main, best score	50.9	53.5	53.4

The first row is the largest improvement, but it comes from Anthropic. In the company’s Claude Code --bare setup at maximum effort, Fable 5.1 solved 52.6% of 70 scientific terminal tasks, compared with 24.7% for Fable 5 and 29.0% for Opus 5. The standard error was about 3.5 to 4.5 percentage points per model, so the Fable 5.1 lead is much larger than the reported uncertainty in this setup. [3] The public Terminal-Bench-Science board did not yet list Fable 5.1 when I checked, which is why I describe this as an Anthropic result rather than a public leaderboard win.

The independent rows tell a calmer story. Cursor places Fable 5.1 first at 73.4%, but the gap is 2.9 points over Fable 5 and 3.4 over Opus. Cursor warns that small score differences may reflect run variance, and its tasks are private examples drawn from real Cursor sessions. [7] [8] Artificial Analysis gives Fable 5.1 the highest GDPval-AA v2 rating at 1,853 Elo. Opus follows at 1,824, and their displayed confidence intervals overlap. Fable 5’s 1,723 is more clearly behind. [9]

Mercor’s APEX-SWE makes the Opus comparison even plainer. Across 200 software cases, Fable 5.1 scores 63.6% and Opus 63.7%, with confidence intervals wider than six points. Fable 5 lands at 58.8%. [19] That is a useful pattern: the successor moves away from Fable 5, while Opus remains close enough that task shape and cost decide the choice.

There is counterevidence too. Cognition’s FrontierCode checks whether maintainers would accept a patch, including its tests, scope, and codebase conventions. Fable 5.1 peaks at 50.9 on the main set at medium, below Fable 5’s 53.5 at xhigh and Opus 5’s 53.4 at medium. [11] Anthropic says higher Fable 5.1 effort can trigger useful but unrequested edits that the benchmark correctly penalizes as out of scope. [3] More work is not always a better patch.

Why the 31.4% AutomationBench win belongs to two models

Zapier’s top AutomationBench row is a deployed Fable 5.1 and Opus 5 system, not a pure Fable score. Opus handled 260 of 657 tasks after the safety classifier intervened, and Zapier includes those completions in the 31.4% result. [12]

strict completion rate

31.4 %

Fable 5.1 plus Opus 5 fallback

tasks handled by Opus

260/657

about 40% of the evaluation

shown cost per task

$2.45

fallback tokens excluded

This is not a reason to discard the result. AutomationBench measures whether an agent leaves a simulated business in the correct state after working across 47 tools, and its final-state checks are deterministic. The combined system ranks first because it completes more of those workflows. The problem begins only when the row is shortened to “Fable 5.1 scores 31.4%.”

Fable’s safeguards are part of the product. Anthropic says biology requests can route to Opus 5, while some cybersecurity requests route to Opus 4.8. [1] In Zapier’s evaluation, Opus then returns control to Fable to finish the task. The displayed $2.45 cost includes Fable usage but excludes the fallback tokens, so it cannot support a clean cost comparison with standalone Opus at $1.27 per task. [12]

The same issue appears more quietly elsewhere. Artificial Analysis labels its Fable 5.1 entries “Default Fallback,” including the number-one GDPval row. [9] A developer choosing the public model cares about the deployed system, so these results are useful. A developer asking which weights reason better needs a different experiment.

Is Fable 5.1 cheaper than Fable 5 or Opus 5?

Fable 5.1 is usually a better value than Fable 5 when the workload reuses context, but Opus 5 remains cheaper by list price. End-to-end cost against either model depends on tokens, cache hits, agent steps, effort, and fallback behavior.

Cursor’s max-effort run is the best case for the upgrade. Fable 5.1 scores 73.4% for $9.64 per attempted task, while Fable 5 scores 70.5% for $17.32. Fable 5.1 uses 72,060 tokens against 103,525, about 30% fewer, so it is both better and 44% cheaper inside this harness. Opus scores 70.0% for $8.23 and 61,838 tokens. [7]

Artificial Analysis finds the opposite token pattern on its nine-part intelligence index. Its max-effort Fable 5.1 run uses about 45,236 output tokens and costs $3.69 per task. Fable 5 uses about 35,565 and costs $3.14, while Opus uses about 40,249 and costs $2.34. Fable 5.1 also takes 285 seconds to its first answer, compared with 121 for Fable 5 and 60 for Opus. [10]

Neither evaluator has to be wrong. Cursor tests ambiguous multi-file coding inside its production agent, while Artificial Analysis combines coding, science, general reasoning, and professional agent work. Their prompts, tools, cache reuse, stopping rules, and graders differ. “Fable 5.1 uses fewer tokens” is true in one harness and false in another. The task cost, not the token rate alone, is the number worth measuring in your own system.

Subscription users face another price. Fable 5.1 is available on paid Claude plans, but access and weekly allowance depend on the plan and seat type. [17] A cheaper API cache hit does not make a long xhigh Claude Code run gentle on a weekly quota.

What do the first Fable 5.1 users think?

There was no reliable consensus in reports posted on September 1, 2026. The credible accounts support three tentative impressions: Fable 5.1 can stay with harder work for longer, it can be easier to read than Fable 5 or Opus 5, and it can consume far more time or quota than the user expected.

I reviewed one Hacker News launch thread with 688 comments and six Reddit threads with 457 comments visible in their public renderings. That 1,145-comment set is self-selected, repetitive, and full of people reacting to the announcement rather than running the model. I used it to find failure modes, not to calculate sentiment. [15] [16]

The positive hands-on comments describe difficult coding work that finished in one run, better recall across long context, and fewer false safety interventions. One developer working on a real C codebase called 5.1 another step up from Fable 5 on larger planned features. A Reddit user reported a working C++ application after a 50-file generation. Neither post includes a controlled baseline or a repository I can inspect, so both remain useful anecdotes rather than benchmark results. [15] [16]

The negative reports are just as concrete. Several users hit a five-hour limit before a long first task finished, and one Max user said a similar multi-agent workload consumed 42% of the weekly allowance on Fable 5.1 versus 20% on Fable 5. Other users disagreed about the prose, with one reporting garbled text after a long context and another finding it shorter and clearer. [15] [16] These accounts do not establish average quota use or writing quality, but they warn against treating the launch claims as a default experience.

Two structured early tests give the reports more context. CodeRabbit evaluated 45 code-review tasks containing 105 known issues. Fable 5.1 reached 61.0% recall against Fable 5’s 61.9%, while precision rose from 32.8% to 37.3% and final comments fell from 253 to 166. It also took 18 minutes 38 seconds per task instead of 12 minutes 32 seconds. CodeRabbit changed its review pipeline between model runs, so this is a direction rather than a clean head-to-head result. [13]

Every tested Fable 5.1 for a week before launch and found comparable agent output to Opus 5 with less than half the tokens and about 60% of the time. The same review records the failures that matter: a 1,000-word limit became 1,288 words, a request for 8 to 12 quotations produced 43, and five of 27 checked quotations did not exist in the source. Opus kept the output limits but timed out twice. [14] Anthropic provided early access but had no editorial input, which makes this more useful than a launch testimonial and less independent than a blind public test.

My read is that Fable 5.1 improved the part of Fable that keeps working, but did not remove the need to set boundaries and verify the result. The model may now reach further before it fails. That is valuable, and it can also make a bad run more expensive.

Should you switch from Fable 5 or Opus 5?

I would move active Fable 5 workloads to 5.1 after a migration check, but I would keep Opus 5 as the default for ordinary coding. Fable 5.1 earns the expensive jobs where a small capability gain can prevent a failed hour or an extra review cycle.

Workload	My starting model	Why
Scoped feature or reproducible bug	Opus 5 at medium or high	Close benchmark results, lower base price, and better discipline in some patch tests
Long refactor after Opus falls short	Fable 5.1 at high	Better long-horizon results without starting at the most expensive effort
Scientific terminal or research workflow	Fable 5.1 at high or xhigh	Its largest documented gains appear on long tool-using work
Work with hard output limits	Opus 5	Early tests show better compliance with counts and formats
Cache-heavy agent with repeated context	Fable 5.1	The $0.25 cache-read rate can change the task cost
Existing Fable 5 integration with editable history	Fable 5 until migrated	Fable 5.1 thinking blocks impose new conversation-history rules

The migration check matters. Fable 5.1 rejects forced tool_choice values such as any or a named tool, and its adaptive thinking cannot be turned off. Older Claude models cannot read Fable 5.1 thinking blocks. For accounts created on or after August 31, 2026, editing the system prompt, tools, or an earlier turn can also invalidate signed thinking blocks. [18] A fallback from Fable 5.1 to Opus may therefore change the conversation state as well as the model.

I would also start below max. CursorBench moves from 69.4% at high to 73.4% at max, while its task cost doubles from $4.80 to $9.64. [7] Anthropic warns that effort labels do not represent the same amount of thinking across different models. [6] The only useful effort setting is the lowest one that meets the acceptance criteria on your own tasks.

Fable 5.1 is the strongest generally available Claude for work that needs the last bit of persistence. Opus 5 is still the easier default to justify. I would move one long-running, expensive workload first, measure accepted output, cache reuse, and quota burn, and only then change the default.