
Anthropic's Claude Fable 5 is the company's first Mythos-class model made broadly available โ a tier that sits above Opus in capability. It launched on June 9, 2026, got pulled offline three days later under US export controls, and came back on July 1 with new safeguards bolted on. That's a lot of change in under a month. Here's a clear breakdown of what's actually new, what's been removed or restricted compared to the previous generation, and what shifted in the recent relaunch.
Fable 5 is Anthropic's fifth model generation, and it's built specifically for longer, harder, more autonomous work than any Claude model before it.
๐ Anthropic: Introducing Claude Fable 5 and Claude Mythos 5 ยท Claude Fable product page
The jump in capability came with real trade-offs versus Opus 4.8, especially for anyone integrating Fable 5 through the API.
1. No More Zero Data Retention Fable 5 and Mythos 5 are both designated "Covered Models" and are not available under zero data retention. Instead, all traffic carries a mandatory 30-day retention window, even on first- and third-party surfaces.
2. Safety Classifiers That Can Refuse Requests Fable 5 introduces safety classifiers that can decline a request outright. This is a structural change for integrations โ a refusal now comes back as a successful response rather than an error, and it reports which classifier triggered it.
3. Automatic Fallback for Flagged Topics Many queries touching cybersecurity or biology don't get answered by Fable 5 at all โ they're automatically routed to Claude Opus 4.8 instead. Developers need to configure a fallback setup to handle this gracefully.
4. No Unique Offensive Cybersecurity Capability Unlike Mythos 5 (its limited-access sibling), Fable 5 was deliberately launched without any unique offensive cybersecurity edge โ the strongest safeguards Anthropic has ever applied to a model.
5. Higher Pricing Fable 5 is priced at $10 per million input tokens and $50 per million output tokens โ the highest published pricing for any generally available Claude model, with a 1.1x multiplier for US-only inference.
6. Distillation Lockout Requests flagged as attempts to distill Fable 5's capabilities into a competing model automatically fall back to Opus 4.8 instead of being served directly.
๐ Claude Platform Docs: Introducing Claude Fable 5 and Claude Mythos 5
Three days after launch, the US government applied export controls to Fable 5 and Mythos 5 after a reported method of bypassing Fable 5's safeguards surfaced โ prompting Anthropic to suspend both models entirely rather than risk serving foreign nationals it couldn't verify in real time. Access was restored on July 1, but not unchanged.
1. A Stronger Jailbreak Classifier Fable 5 came back with a new classifier that blocks the specific bypass technique in more than 99% of cases.
2. More False Positives on Routine Work That same classifier flags some ordinary coding and debugging requests more often than before โ a trade-off Anthropic says it will keep refining.
3. A Shared Industry Jailbreak Framework Anthropic is working with Amazon, Microsoft, Google, and other partners on a common way to assess and respond to jailbreak severity across the industry.
4. Deeper Government Collaboration Anthropic has committed to more pre-release testing, information sharing on jailbreaks and misuse, and joint research with the US government going forward.
5. Temporary Usage Caps Instead of Full Restoration Rather than reopening Fable 5 to unlimited use immediately, Anthropic capped it at up to 50% of weekly usage limits for Pro, Max, Team, and select Enterprise plans โ a window that's been extended once already, from July 7 to July 12 โ before shifting to paid usage credits.
๐ Anthropic: Redeploying Claude Fable 5
Fable 5 represents a real jump in what Claude can do unsupervised โ longer tasks, better judgment, less correction needed. But it's also the first Claude model built around the idea that some requests should simply be declined rather than answered, and the first to carry mandatory data retention as a condition of that added capability. The redeployment saga makes the trade-off explicit: more power came bundled with more oversight, both from Anthropic and from the US government. Whether that balance holds up under real-world use is still playing out in usage caps, classifier tuning, and the industry-wide jailbreak framework taking shape right now.