Anthropic launched Claude Fable 5.1 (and Mythos 5.1, same weights, tighter-gated safeguards) on September 1, 2026. It is the new generally-available frontier for agentic coding and knowledge work: 1M context, adaptive thinking steered by effort, at $10 in / $50 out per MTok with $0.25 cache reads.
I tested the announcement against the official docs so you do not have to: verified specs, lab-reported benchmarks, working API code on claude-fable-5-1, and where Opus 5 (July 24) still wins as the cheaper fallback.
1. Context: Why Fable 5.1 Matters Right Now
Anthropic shipped Fable 5 and Mythos 5 in June, Sonnet 5 on June 30, Opus 5 on July 24 β then Fable 5.1 and Mythos 5.1 on September 1, 2026. Fable 5.1 is the same base price as Fable 5 ($10 in / $50 out per MTok) but cuts cache reads 75% to $0.25/MTok, so Anthropic prices typical workloads ~25% lower and highly agentic runs up to ~45% lower (lab-measured over August usage, token-billed only). Opus 5 ($5/$25) stays the cheaper starting point: the docs say start with Opus 5 and reach for Fable 5.1 when Opus 5 at higher effort still falls short.
Do Not Confuse the Tiers
Fable 5.1 is the generally-available frontier above Opus; Mythos 5.1 shares its weights and pricing but is invitation-only via Project Glasswing for vetted cyber/life-science work. Sonnet 5 is the fast workhorse. Opus 5 is the cheaper agentic baseline to beat first.
The headline control is adaptive thinking, always on for Fable 5.1 and steered per request by effort (low, medium, high, xhigh, max; default high). It decides how much to think, including between tool calls, while max_tokens remains the hard cap. New versus Fable 5: per-message effort and turn-scoped system messages (beta), readable progress updates between tool calls (display: updates, beta), and content provenance.
2. Four Implications for Developers
Beyond the marketing, here is what actually changes in the way you build with Claude:
Start on Opus 5, Escalate to Fable 5.1
opus 5 β fable 5.1
Official guidance: start most workloads on Opus 5 ($5/$25) and escalate to claude-fable-5-1 only when Opus 5 at higher effort still falls short on your evals.
Long-Horizon Agents That Stay on Task
agentic coding
Fable 5.1 is positioned for demanding reasoning and long-horizon agentic work: long-running coding, multistep research, and document/spreadsheet/slide work with progress updates between tool calls.
1M Context at Standard Pricing
1M tokens Β· 128K output
Fable 5.1 keeps a 1M-token window (default and max) at standard per-token pricing with 128K max output β whole-repo reasoning without a long-context surcharge.
Cache Reads Are the Price Cut
$0.25 / MTok reads
Base input/output match Fable 5, but cache reads cost 2.5% of base input ($0.25/MTok). Context-heavy agent loops that re-read cached prefixes capture the ~25β45% savings; no reusable context, no saving.
The One-Sentence Takeaway
Fable 5.1 is an endurance-and-economics upgrade: same $10/$50 base as Fable 5, cache reads at a quarter of the cost, adaptive thinking always on. Lab-reported: 52.6% on Terminal-Bench-Science 0.1 vs 24.7% (Fable 5) and 29.0% (Opus 5) β verify on your own evals before migrating.
3. The Verified Numbers: Benchmarks and Lineup
Every figure below comes from Anthropic's official launch page or the official Fable 5.1 model docs. Benchmark scores are Anthropic lab-reported (their harness, their framing) β treat them as directional until your own evals confirm.
π Benchmarks (Anthropic Lab-Reported)
Terminal-Bench-Science 0.1
Lab-reported agentic science tasks in a terminal: Fable 5.1 at 52.6% vs Fable 5 at 24.7% vs Opus 5 at 29.0% (Anthropic harness, Sep 2026). More than doubles its predecessor.
Effective cost vs Fable 5
Lab-reported billing estimate: ~25% cheaper typical, up to ~45% cheaper highly agentic, from cache reads at $0.25/MTok β token-billed usage only, measured over August 2026 usage.
Frontier coding posture
Lab-reported positioning: strongest generally-available Claude for long-running agentic coding and multistep research; Mythos 5.1 identical weights for vetted programs.
Opus 5 anchor (Jul 24)
Lab-reported vs-anterior anchor: Opus 5 doubled Opus 4.8 on Frontier-Bench and sat within 0.5% of Fable 5 on CursorBench 3.2 at half the cost β the baseline Fable 5.1 now has to beat on your evals.
Independent cost caveat
Third-party trackers note max-effort runs can cost more per task (more output tokens) even with cheaper cache reads β sweep effort levels on your own workload.
Cutoff June 2026
Reliable knowledge cutoff June 2026 (Opus 5: May 2026). Same tokenizer as Fable 5; ~30% more tokens than pre-Opus-4.7 models for identical text.
𧬠What's New vs Fable 5 (Docs)
Adaptive always on
Only thinking mode on Fable 5.1; steer depth with effort. budget_tokens/disabled rejected with 400.
Per-message effort
Beta: change effort mid-conversation via system message and keep the prompt cache.
Progress updates
Beta display: updates β readable status lines between tool calls; reasoning stays hidden.
π° Lineup and Pricing (Official Docs)
claude-fable-5-1
$10 in / $50 out per MTok Β· 1M context Β· 128K out Β· cutoff Jun 2026
claude-mythos-5-1
Same $10/$50 specs Β· Glasswing invite-only
claude-opus-5
$5 in / $25 out per MTok Β· 1M context Β· cheaper baseline
claude-sonnet-5
$2 in / $10 out per MTok Β· workhorse default
Cache reads
$0.25/MTok on 5.1 (2.5% of input) Β· 75% cut vs Fable 5
Batch + writes
Batch 50% off Β· 5m writes $12.50 Β· 1h writes $20
Pricing Tip
The saving lives in cache reads: keep long agentic sessions on a stable cached prefix and constant effort so hits accumulate. Short one-shot calls with no reusable context see no discount β those belong on Opus 5 or Sonnet 5.
4. Ship It: Real API Code From the Official Docs
The snippets below follow the official Messages API and effort docs exactly for claude-fable-5-1. Top-level output_config.effort needs no beta header; high is the default. Adaptive thinking is always on β do not send thinking budget_tokens/disabled.
π» Copy-Paste Quickstart
cURL
curl https://api.anthropic.com/v1/messages \
-H "x-api-key: $ANTHROPIC_API_KEY" \
-H "anthropic-version: 2023-06-01" \
-H "content-type: application/json" \
-d '{
"model": "claude-fable-5-1",
"max_tokens": 4096,
"messages": [{
"role": "user",
"content": "Refactor this function for clarity"
}],
"output_config": {"effort": "medium"}
}'Python
import anthropic
client = anthropic.Anthropic()
response = client.messages.create(
model="claude-fable-5-1",
max_tokens=4096,
messages=[
{"role": "user", "content": "Refactor this function for clarity"}
],
output_config={"effort": "medium"},
)
for block in response.content:
if block.type == "text":
print(block.text)πͺ First Call in 5 Minutes
1. Pin the model ID
Use claude-fable-5-1 exactly (Mythos: claude-mythos-5-1, Glasswing only). Dateless IDs are pinned snapshots, not moving pointers.
2. Start at high effort
It is the default on Fable 5.1. Only step down to medium or low after your own evals confirm quality holds.
3. Give max_tokens room
At xhigh or max effort, start around 64k so the model has space to think and call tools; max_tokens caps thinking plus text.
4. Keep effort constant in cached chats
Changing top-level effort between requests restarts the prompt cache. On Fable 5.1 prefer per-message effort (beta header) to keep the cache.
5. Do not fight adaptive thinking
Omit thinking or send {type: adaptive}. Prefilling the assistant turn, custom temperature/top_p/top_k, and forced tool use return 400 on Fable 5.1.
ποΈ Effort Levels
low
Subagents and routine tasks where speed and cost beat depth.
medium
Balanced default for production traffic once evals pass.
high
API default. Complex reasoning, hard coding, agent loops.
xhigh / max
Long-horizon work over 30 minutes or frontier-grade problems with million-token budgets.
5. Safeguards and Platform Updates
Fable 5.1 and Mythos 5.1 share identical weights with different safeguards. Fable 5.1 is generally available with extra blocks on high-risk biology and cybersecurity dual-use work; Mythos 5.1 relaxes those for vetted orgs (Life Sciences verification live, Cyber verification expanding via Project Glasswing). The practical changes for builders are these:
Same Model, Two Safeguard Tiers
Fable 5.1 blocks select bio/cyber dual-use tasks (e.g. penetration testing, exploit generation, binary-based vuln scanning redirect to Opus-class handling); Mythos 5.1 keeps full capabilities for vetted Glasswing participants.
Vuln-Finding Now Allowed on Fable
Fable 5.1 may now be used for identifying software vulnerabilities, with more precise safeguards that block fewer basic biology questions than Fable 5 did.
Mid-Conversation System + Tool Changes
Turn-scoped system messages and mid-conversation tool changes are supported (beta) without invalidating the cache. Earlier models cannot read Fable 5.1 thinking blocks; editing earlier turns invalidates them.
Enterprise Frontier Safeguards
New EFS architecture keeps monitoring data inside customer-controlled cloud storage (phased rollout this fall); eligible Fable 5.1 users get zero data retention until EFS lands.
Opus 5 as the Cost Fallback
Docs position Opus 5 ($5/$25) as the default start; flagged or over-budget Fable 5.1 traffic can fall back to Opus-class models. Fast mode and batch (50% off) still apply where offered.
6. What to Do This Week
A concrete three-step plan to turn this release into shipped improvements before next Monday:
βοΈ Day 1β2: Benchmark Fable 5.1 vs Opus 5
- 1. Pin claude-fable-5-1 in staging and replay your 10 hardest recent agent traces (keep an Opus 5 branch as control)
- 2. Run each trace at high, then medium effort, and log cost per resolved task including cache-read share
- 3. Record where Fable 5.1 finishes long-horizon runs that Opus 5 at xhigh still drops
π Day 3β4: Wire Escalation Into Production
- Routing: Default traffic to Opus 5; escalate to Fable 5.1 only when Opus 5 at higher effort fails your evals
- Caching: Freeze cached prefixes and use per-message effort (beta) so $0.25/MTok reads compound
- Updates: Opt into display: updates (beta) so long agentic turns stream status instead of going silent
π Day 5: Decide the Migration
- Compare: Fable 5.1 cost-per-solved-task against Opus 5 β not per-token price, per finished result
- Migrate: Promote Fable 5.1 for long-horizon agentic work it wins clearly, keep Opus 5/Sonnet 5 elsewhere
- Document: Write down your effort map and cache strategy so the next 5.x swap is a config change
7. Honest Limits: Read Before You Migrate
No launch chart tells the whole story. Anthropic's savings (~25% typical, ~45% agentic) are lab-measured on their own August usage at default effort for token-billed workloads, and independent trackers show max-effort runs can cost more per task via extra output tokens. Calibrate with your own evals:
β Reach for Fable 5.1
- β’ Long-horizon agentic coding and multistep research Opus 5 at xhigh still fails
- β’ Context-heavy agent loops where $0.25/MTok cache reads dominate the bill
- β’ Whole-repo work needing 1M context at standard pricing plus 128K output
- β’ Document/spreadsheet/slide pipelines needing judgment on ambiguous work
- β’ Vuln-identification workflows allowed on Fable 5.1 (non-exploit)
- β’ Any workload where Fable 5 was current and evals confirm gains
β Probably Keep What You Have
- β’ Well-scoped tasks where Opus 5 or Sonnet 5 already passes β 2β5x cheaper per token
- β’ One-shot calls with no reusable context (no cache-read saving to capture)
- β’ Exploit-generation or restricted bio/cyber work: needs Mythos 5.1 / Glasswing vetting
- β’ Latency-sensitive traffic: Fable 5.1 comparative latency is Slower
- β’ Benchmark-chasing without a production eval of your own
- β’ Migrating on launch day without replaying your hardest traces first
Golden rule
Effort is soft guidance, not a token budget, and max_tokens is the hard cap: sweep effort levels on your own evals, watch output-token growth at max, and let cost-per-solved-task β not launch charts β decide.
Conclusion
Claude Fable 5.1 is an endurance-and-economics release: same $10/$50 base as Fable 5, cache reads quartered to $0.25/MTok, adaptive thinking always on with effort steering β lab-reported at 52.6% on Terminal-Bench-Science 0.1 versus 24.7% (Fable 5) and 29.0% (Opus 5).
My verdict as a builder: keep Opus 5 as your cost-effective default, escalate to Fable 5.1 for the long-horizon agentic work Opus 5 at higher effort still fails, and let your own cost-per-solved-task numbers decide the migration.
Cheat Sheet: Fable 5.1 at a Glance
Model
- β’ claude-fable-5-1
- β’ Launched Sep 1, 2026
- β’ Frontier above Opus 5
Specs & Price
- β’ $10 in / $50 out per MTok
- β’ 1M context Β· 128K output
- β’ Cache reads $0.25 Β· effort high
Start Here
- β’ Official announcement
- β’ Fable 5.1 model docs
- β’ Effort parameter docs
Sources
Every claim in this article traces to one of these official pages. Benchmarks are Anthropic lab-reported unless noted.
- Anthropic β Introducing Fable 5.1 and Mythos 5.1 (Sep 1, 2026)
- Claude docs β Fable 5.1 overview (ID, pricing, context, effort)
- Claude docs β Effort parameter (levels, code samples)
- Claude docs β What's new in Fable 5.1 (breaking/additive changes)
- Anthropic β Opus 5 launch (Jul 24, 2026, vs-anterior anchor)



