Update (July 3, 2026): Claude Fable 5 is back. The US Commerce Department lifted the export controls on June 30, and Anthropic restored global access on July 1 across the Claude API, claude.ai, Claude Code and Claude Cowork, with AWS Bedrock, Google Cloud and Microsoft Foundry re-enabled the same day. See the new section below for the conditions that remain, and note the included-usage window on paid plans ends July 7.
On June 9, 2026, Anthropic launched Claude Fable 5, the first publicly available model in its new Mythos class and, in the company's own framing, the most capable model it had ever released to the general public. Seventy-two hours later, it was gone. On the evening of Friday, June 12, a United States government export-control directive forced Anthropic to disable both Fable 5 and its sibling Claude Mythos 5: not in one country, but for every user on the planet.
This was not a bug, an outage, or a billing dispute. It was a national-security order from the US Department of Commerce, delivered to CEO Dario Amodei at 5:21 PM ET, that Anthropic publicly disagreed with, and ultimately got reversed. On June 30, 2026, the Commerce Department lifted the controls, and on July 1 Fable 5 returned to users worldwide, 19 days after it went dark.
Below is the most complete, sourced account we could assemble: what Fable 5 actually is, the exact sequence that led to the shutdown, what the 'jailbreak' at the center of it really was (it is more ironic than you would expect), how the model came back and under what conditions, and the architecture lesson every team shipping AI should take from it.
The events unfolded in days, not weeks, and the resolution took less than three. Here is the full sequence pieced together from Anthropic's own statements and reporting by Fortune, TechCrunch, Axios, Politico, Semafor, CNBC and Forbes:
The directive barred access by any foreign national, whether inside or outside the United States, and including Anthropic's own foreign-born employees. Because the company could not filter users by nationality in real time, it chose to switch both models off for everyone rather than risk non-compliance.
On June 30, 2026, 18 days after the directive, the Commerce Department withdrew the export controls on Fable 5 and Mythos 5, removing the license requirement for both models. Anthropic announced the reversal in a post titled 'Redeploying Claude Fable 5' and restored access the next day, July 1: globally and all at once, not as a phased rollout. Fable 5 is live again on the Claude API, claude.ai (Pro, Max, Team and Enterprise plans), Claude Code and Claude Cowork, and back on AWS Bedrock, Google Cloud and Microsoft Foundry.
Claude Mythos 5 followed a narrower path: the government approved restoring it on June 26, but only for a set of US organizations in Project Glasswing. It remains invitation-only, with no self-serve sign-up, and access for international Glasswing partners is still being coordinated with the government.
As part of the resolution, Anthropic committed to proactive risk detection, collaboration with the government on security protocols and standards, and prompt reporting of malicious activity. It is also proposing an industry-wide framework for scoring jailbreak severity together with Amazon, Microsoft, Google and other Project Glasswing partners.
The trigger was a reported jailbreak of Fable 5's safeguards. But the details, in Anthropic's own words, are surprising. The company described it as 'a narrow, non-universal jailbreak, which essentially consists of asking the model to read a specific codebase and fix any software flaws.'
That is the irony at the heart of this story. The Mythos class was built to be the strongest cybersecurity model in the world: its sibling, Mythos 5, is deployed to roughly 150 organizations in 15+ countries through Project Glasswing specifically to find and patch vulnerabilities in critical software. The very capability that makes it a world-class defender (reasoning through a codebase to surface exploitable flaws) is dual-use. Pointed the other way, it is exactly what a state-level attacker would want.
Sacks said a 'highly credible, trusted partner of both Anthropic and the government' had identified the jailbreak in Fable 5's guardrails, and that after Amodei declined to fix or pull the model, the administration issued the export control 'reluctantly.' Semafor reported the government suspected a China-linked group may have already used the jailbreak Amazon discovered, though the evidence was described as unclear, and Anthropic disputes that the White House ever raised Chinese access in their conversations.
Anthropic's broader position is that no model is perfectly jailbreak-proof: it states that 'perfect jailbreak resistance is not currently possible for any model provider,' while maintaining that Fable's safeguards are 'substantially more effective than those of any previously deployed model.'
Fable 5 and Mythos 5 share the same underlying model and published specifications; Fable is the public-facing variant with additional safeguards. For context on what's back online:
On the numbers Anthropic and early third-party testers published, Fable 5 sits at the frontier:
Since July 1, calls to claude-fable-5 work again: same model ID, same pricing, same specs. But 'back online' does not mean 'back to normal'. Before you route production traffic to it again, check these four things:
The Fable 5 suspension is a textbook example of a risk most teams underestimate: model availability is not guaranteed. A model you depend on can vanish overnight: through deprecation, a price change, a capacity limit, or, as here, a government order entirely outside your control. And this time, the warning was 90 minutes.
Teams that wired Fable 5 in as a single hardcoded dependency had production break with no real notice. Teams that built vendor-agnostic architectures barely noticed: a fallback engaged and traffic kept flowing. That difference is an engineering decision you make before the incident, not after it.
We don't ship demos: we put AI agents and automations into production, and we design them so that no single model is a single point of failure. The Fable 5 suspension is exactly the scenario our architectures are built to absorb.
If the Fable 5 episode made you realize how exposed your AI stack is to a single vendor, that's exactly the problem we solve. Let's design an architecture that keeps working no matter which model is online tomorrow.
Claude Fable 5 was, by Anthropic's own account, one of the safest and most capable models ever deployed, and it was still pulled from the market three days after launch by a government order nobody could predict, over a 'jailbreak' that amounted to asking it to fix software flaws. Nineteen days later it was back, just as suddenly. That tension between capability and control is the whole story.
The happy ending doesn't change the lesson. The teams hurt by this weren't the ones using Fable 5: they were the ones who could only use Fable 5. And the teams re-enabling it this week without friction are the ones whose architecture made the outage a routing change. In frontier AI, the durable advantage isn't picking the best model: it's building systems that survive losing it.
If you're integrating frontier models into a product, an agent, or an automation, we can help you design the routing, fallbacks and self-hosted options that turn a vendor outage into a non-event.
Yes. The US Commerce Department lifted the export controls on June 30, 2026, and Anthropic restored global access on July 1: on the Claude API, claude.ai (Pro, Max, Team and Enterprise), Claude Code, Claude Cowork, AWS Bedrock, Google Cloud and Microsoft Foundry.
The US Department of Commerce issued an export-control directive on June 12, 2026, citing national-security authorities, after a reported jailbreak of Fable 5's safeguards was flagged to the White House. Anthropic disabled the models globally because it could not restrict access by nationality in real time.
19 days: from the evening of June 12 to July 1, 2026. The Commerce Department lifted the controls on June 30, and Anthropic redeployed the model globally, all at once, the next day.
Through July 7, 2026. On Pro, Max, Team and select Enterprise plans, Fable 5 is included for up to 50% of weekly usage limits until that date; afterwards it moves to usage credits at $10/$50 per million input/output tokens.
They share the same underlying model. Fable 5 is the public-facing version with additional safeguards and is generally available again. Mythos 5 was restored earlier (June 26) but only for approved US organizations in Project Glasswing. It remains invitation-only, with international access still being coordinated with the government.
Yes. Both models keep the mandatory 30-day data-retention policy (no zero-retention option; on Bedrock it requires an explicit provider_data_share opt-in), and the cybersecurity and biology classifiers remain active with materially higher refusal rates than other Claude models. Pricing is unchanged at $10/$50 per million tokens.