Anthropic Just Split the Frontier in Two
Fable 5 is the model we get. Mythos 5 is the model we don’t. The gap between them is the product strategy.
Jun 12, 2026, critical update: The U.S. government, citing national security authorities, issued an export control directive suspending access to Fable 5 and Mythos 5 for foreign nationals, regardless of whether they are inside or outside the United States, including foreign-national Anthropic employees. The net effect is that Anthropic suspended customer access to Fable 5 and Mythos 5 altogether to ensure compliance.
My original post below:
TL;DR: Anthropic shipped Claude Fable 5 on June 9, 2026, the same underlying model as Claude Mythos 5, with a classifier layer that re-routes 5% of high-risk queries to Opus 4.8. It's $10 input / $50 output per million tokens, exactly 2x Opus 4.8. The buried trap: every "show your reasoning" prompt from the GPT-4 era silently downgrades Fable 5 to Opus 4.8 via the reasoning_extraction classifier. You don't pay Fable prices for the downgrade, but you do pay in stamina, context, and the half-hour you spent assuming a long-running agent was running on Fable. Nothing in the API warns you before it happens. Here's the routing playbook and the math on when 2x is worth it.
When a company announces two products from one model, the model is no longer the only thing being productized.
Today, Anthropic launched Claude Fable 5 and Claude Mythos 5.
Same underlying model. Different doors. Different rules.
This must be an interesting time to be a PM at Anthropic.
The model creates the capability, but the product is shaped in the access layer: segments, permissions, routing, eligibility, pricing, governance, and trust.
For builders, that access layer is part of the product we are building on top of.
What’s Inside
What Fable 5 Is
Fable 5 is the version you and I get: Anthropic’s most capable generally available model, built for software engineering, knowledge work, vision, scientific research, and long-running agentic tasks.
In API terms, the model ID is claude-fable-5. It supports a 1M token context window by default and up to 128k output tokens per request.
And Fable 5’s advantage seems to grow with task length.
Short tasks test fluency. Long tasks test endurance: whether the model can hold context, recover from ambiguity, follow constraints, inspect its own work, and keep going after the easy part is over.
Software migrations. Financial analysis. Chart and table reasoning. Vision-heavy coding.
Long tasks are also where enterprises burn money: handoffs, review loops, retries, context rebuilding, and humans babysitting work that was supposed to be automated. Less supervision when work gets long enough to become expensive is where the real enterprise value begins.
Hey, I’m Karo Zieminski 🤗
AI Product Manager and builder.
I write Product with Attitude, an AI newsletter for thousands of subscribers developing critical AI literacy the only way it sticks: through practice.
We don’t just use AI. We build workflows, automations, and products with it, while studying how AI itself is built, positioned, and woven into our work.
If you’re new here, welcome! Here’s what you might have missed:
What Mythos 5 Is
Mythos 5 is the same model with safeguards lifted in selected areas. You can’t buy it.
This is frontier AI with a guest list. Access is limited because the capability can do real damage in the wrong context. The same skills that help defenders can also help attackers.
Anthropic first introduced Mythos as a limited preview in April. At the time, only a small number of partners could access it through Project Glasswing, including the US government and trusted cyberdefense partners.
Last week, Anthropic widened access to hundreds of organizations in 15 countries.
But this is still not open access.
My PM read: gated access is a trust-as-a-feature play. Anthropic created a restricted tier that money cannot unlock. Only vetting can.
I personally think limiting access to capabilities considered dangerous can be a good idea. But I would not be surprised if this creates backlash.
A private company is now deciding who gets access to certain frontier AI capabilities, using criteria the public cannot fully inspect.
Who counts as “trusted”?
What does “trusted” mean?
These are difficult ethical choices. Open access can create real harm. Restricted access can create private gatekeeping.
Again: an interesting time to be on Anthropic’s product team.
The New AI Safety Pattern: Route, Don’t Refuse
Fable 5 comes with new safeguards for cybersecurity, biology, chemistry, and model distillation.
When a request triggers those safeguards, Fable 5 does not simply refuse. It routes the response through Claude Opus 4.8 instead.
Luckily, we won't be charged Fable prices for rerouted requests.
My PM read: routing, not refusing, is graceful degradation applied to safety. Refusal is a dead end in the user journey. Fallback keeps the session alive.
I wouldn’t be surprised if other labs copy this quickly.
But graceful degradation is still degradation. If an agent starts on Fable 5 and finishes on Opus 4.8, the product may keep moving while you lose the capability you selected the model for.
Build Like Task Length Is the New Benchmark
For builders, the interesting part is Fable 5’s stamina.
We can use it to audit old codebases, which I’m planning to do for all my 2025 builds.
We can use it to migrate systems.
We can use it to reason through charts, tables, screenshots, and messy product flows without resetting the context every five minutes.
And vision-heavy coding gets fun here too. If Fable 5 can reliably build from screenshots, tools like Magic Patterns will need a new moat.
My AI builder read: If task stamina is the new axis of competition, our evaluation criteria need to change with it.
For builders, the winning model is not always the one with the best answer on the first turn, but the one that can preserve context, follow constraints, recover from ambiguity, and keep going.
My critical AI literacy read: longer autonomous runs mean longer stretches where no human is checking the work.
So design checkpoints. Know where the human review must happen, and don’t automate that moment away.
The “Show Your Reasoning” Trap
I found this in Anthropic’s prompting guide, and I’m not sure how I feel about it.
A common way to get better answers from AI models is to ask them to show their reasoning.
Things like:
Show me your reasoning.Walk me through your thinking.Think step by step and show your work.But Anthropic’s documentation says that if a prompt asks Fable 5 to echo, transcribe, or explain its internal reasoning in the final answer, it can trigger a safety category called reasoning_extraction, causing what the docs call "elevated fallbacks to Claude Opus 4.8."
In plain English: the model may treat the prompt as asking for something it shouldn’t reveal, then route the response to Claude Opus 4.8.
I still want to understand how the models work, so instead of asking for reasoning, I’ll be asking for sources, assumptions, and checks. Let’s see if that works.
My critical AI literacy read: prompt patterns are not portable forever.
The same instruction that improves one model can create routing, reliability, and cost problems on another.
I explained this more in my prompt engineering article:
The June 23 Paywall Flip
Fourteen days from today, the access economics change.
Through June 22, Fable 5 is included at no extra cost on Pro, Max, Team, and seat-based Enterprise plans.
Starting June 23, Anthropic says Fable 5 will require usage credits unless capacity allows the included window to be extended.
After that, subscription users keep access through usage credits unless Anthropic extends the included window. Anthropic says it will restore Fable 5 as a standard part of subscription plans as quickly as possible but no date is promised.
What this means for builders:
Teams integrating Fable 5 this week are running production code on a model that becomes pay-per-use in two weeks.
Engineering managers who don’t read launch posts are about to get a surprise spend report on July 1.
Cost monitoring on Claude Code, Cursor, and any subscription-based Fable surface needs to be in place by June 22 at 11:59 PT.
One r/ClaudeAI commenter estimated typical agentic use at “approximately $5,000 per month” once metered billing kicks in. That number is anecdotal, but the point is this: once agentic usage moves onto metered billing, the default model stops being a preference and becomes a cost-control decision.
My PM read: the real adoption test starts when the included window ends. Free-included-then-credits is a habituation funnel.
Anthropic gets two weeks to make Fable 5 feel like the default, then the paywall measures how much we actually miss it.
My critical AI literacy read: “included for now” is a pricing experiment we are participating in, whether we notice it or not.
Decide before June 23 which workflows truly need Fable 5.
Default model choice is about to become a cost-control decision.
When Fable 5 Earns the 2x Premium
Stripe tested Fable 5 on a 50-million-line Ruby codebase migration.
Anthropic says the work would have taken a whole engineering team more than two months by hand.
Fable 5 completed it in one day.
These are vendor and partner anecdotes, not independently verified results. Useful signal, yes. Independent proof, no.
Even with that caveat, here is the rough business math.
A four-person engineering team working for two months can easily cost around $384,000, once salary, benefits, tools, management, and overhead are included.
If Fable 5 can do the same migration for roughly $1,000 in model usage, the economics get hard to ignore.
On that single task, the return is about 384x.
This is rough directional math, not audited ROI.
But it shows why Fable 5 can earn the premium on long, expensive engineering work.
By that same logic, it doesn’t earn the premium by default.
For shorter workflows, simple automation, high-safety-routing traffic, or anything requiring zero data retention, use a cheaper default model.
Claude Fable 5 vs Mythos 5 vs Opus 4.8
Here is the comparison I would keep next to the model picker.
The Fable Routing Decision
Use Fable 5 only when the answer is yes / no / no.
Yes: the task is long, multi-step, agentic, or memory-heavy.
No: the workload is unlikely to trigger safety routing.
No: zero data retention is not required.
Everything else defaults to Opus 4.8.
Fable 5 is for the work where stamina changes the economics. Opus 4.8 is for the work where reliability, cost control, or retention constraints matter more.
The Mandatory 30-Day Retention Override
Fable 5 and Mythos 5 are designated Covered Models, meaning they’re treated as higher-risk models under Anthropic’s rules.
Anthropic keeps usage data for these models for 30 days, no matter how customers access them. There is no option to turn that retention off.
Even companies that previously had “zero data retention” agreements with Anthropic don’t get that option for these models.
What this means for enterprise procurement:
SOC 2 reviews. “Does this AI provider retain customer data?” is no longer a simple checkbox question for Fable 5 traffic.
EU AI Act preparation. Mandatory retention plus human review creates new disclosure, logging, and governance surfaces for customer-facing AI features touching EU users.
Industry compliance frameworks. HIPAA, FINRA, SEC, and similar reviews now have to account for retained prompts and outputs sitting in a 30-day window outside the customer’s direct control.
Harvey’s customer-facing language on launch day: “Anthropic will retain data and contents (inputs, outputs, and documents) and may review such data for safety reasons.”
That’s the language your legal team will read. Plan for it.
For builders: don’t make Fable 5 the default route for sensitive customer data unless retention has been reviewed as part of the product design.
When Your Product Inherits the Model Provider’s Rules
Fable 5 may be a preview of how frontier AI gets packaged from here: one model family, different access levels, different safeguards, different trust boundaries, and different risk profiles.
If that pattern holds, capability tiers will be defined by trust, not just price.
And if you’re building on top of these models, your product now inherits someone else’s access policy.
Your user doesn’t care that Anthropic made the routing choice. If your product promised Fable-level work and the workflow fell back, that’s your product experience now.
Map that dependency before it maps you.
FAQ for Builders
What is Claude Fable 5?
Claude Fable 5 is Anthropic’s most capable generally available model, built for long-running coding, agentic tasks, knowledge work, vision, and scientific research. It is a Mythos-class model made available to the public with additional safeguards.
Is Claude Fable 5 the same as Claude Mythos 5?
It shares the same underlying model. Mythos 5 has safeguards lifted in selected areas and is limited to approved users through Project Glasswing and trusted access programs.
What is the Claude Fable 5 model ID?
The API model ID is claude-fable-5. Anthropic’s docs say Fable 5 supports a 1M token context window by default and up to 128k output tokens per request.
How much does Claude Fable 5 cost?
Anthropic lists Fable 5 at $10 per million input tokens and $50 per million output tokens. That price makes routing discipline mandatory for teams running long agentic workflows.
When should builders use Claude Fable 5?
Use Fable 5 when task stamina changes the economics: long code migrations, repo audits, complex document work, vision-heavy builds, or agentic workflows where context preservation matters. Do not use it as the default for short tasks, sensitive zero-retention work, or workflows likely to trigger safety routing.
Why does Claude Fable 5 route to Opus 4.8?
Fable 5 uses safety classifiers for areas including cybersecurity, biology, chemistry, model distillation, and hidden-reasoning extraction. When a request triggers those classifiers, Anthropic’s docs say requests can refuse or fall back to Claude Opus 4.8 depending on configuration.
Does Claude Fable 5 support zero data retention?
No. Anthropic designates Fable 5 and Mythos 5 as Covered Models with 30-day retention for prompts and outputs. Organizations with zero data retention requirements need a separate routing policy.
Keep Reading
WHY SUBSCRIBE ・YOUR BENEFITS・ TOOLS I BUILT・CLAUDE HUB・PERPLEXITY HUB ・VIBE CODING HUB
Thanks for the summary, Karo! I have spent the morning using Fable to build out a complete, entirely new visual brand in a regular chat (not for Daring Next!). I have had a frustrating few days in Sonnet/ChatGPT and Fable just blew it out of the water - it knew exactly what I wanted, read Skills with no prompting and it just seems like a really really clever and efficient colleague who is always on the money. I thought I would hit a token wall quickly but so far so good! I can't wait to make the most of it in the next 14 days!
Fantastic breakdown as usual Karo! ❤️
I was telling Joel I don't think I'd pay for Fable after the 22nd but then again it's probably gonna cost an arm and a leg hahaha. I'm super curious to see how experts use it for more advanced workflows!