Claude Fable 5 lasted three days in general availability. On June 12, 2026, the US government issued an export-control directive requiring Anthropic to suspend access to Fable 5 and Mythos 5 for any foreign national—inside or outside the United States. Because Anthropic cannot enforce nationality at the model layer without blocking everyone, both models went offline globally the same evening. API calls to claude-fable-5 now return 404 with a message to use Opus 4.8 instead.
What Triggered the Shutdown
Anthropic received the directive at 5:21 PM ET on June 12. The letter cited national security authorities but, per Anthropic's public statement, did not include specific technical details. The company's understanding is that officials became aware of a potential jailbreak—a technique that could bypass Fable 5's safety classifiers and expose underlying Mythos-class cyber capabilities.
Anthropic disputes that a narrow potential jailbreak should trigger recall of a commercial model deployed to hundreds of millions of users. It noted the demonstrated technique identified relatively minor, previously known vulnerabilities—and that other publicly available frontier models could find similar issues without a bypass. The company is complying with the legal directive while arguing the standard, if applied industry-wide, would effectively halt new frontier deployments.
Surfaces Affected
The suspension is not limited to claude.ai. Every integration that shipped Fable 5 in the launch window is impacted:
- Claude API and Claude Code —
claude-fable-5andclaude-mythos-5return errors; Opus 4.8, Sonnet 4.6, and Haiku 4.5 remain available. - GitHub Copilot — access suspended across all Copilot experiences effective June 12, per an editor's note on the launch changelog.
- Cloud platforms — AWS Bedrock, Google Vertex AI, and Microsoft Foundry deployments of Fable 5 are offline pending remediation.
- Project Glasswing — Mythos 5 partners lose access alongside the public Fable tier.
All other Claude models continue under existing data-retention policies. Only Mythos-class systems carried the mandatory 30-day retention requirement that had already caused friction with enterprise buyers before the government order arrived.
The Governance Collision
Fable 5's launch week exposed a tension that predates the export order. Microsoft reportedly blocked internal employee access to Fable 5 in Copilot because the model's 30-day prompt retention conflicted with Zero Data Retention promises on other Claude tiers. Copilot Business and Enterprise admins had to opt in explicitly. That split—model available versus model approved—is now the enterprise default for frontier releases.
The export directive escalates that from procurement caution to hard outage. Teams that migrated production agent workflows to Fable 5 during the free window through June 22 need an immediate fallback plan.
What Developers Should Do Now
- Re-point model IDs. Replace
claude-fable-5withclaude-opus-4-8in API configs, Claude Code settings, and any CI that pinned Fable 5 during the launch window. - Audit Copilot org policies. If you enabled the Fable 5 policy before June 12, expect it to have no effect until Anthropic and GitHub restore access—verify which model your team is actually running.
- Do not assume a quick return. Anthropic says it is working to restore access but provides no firm timeline. Reporting around the order suggests officials want additional security hardening before re-enablement.
The practical read: Fable 5 proved the capability tier developers wanted—Stripe-scale migrations, long-horizon agent runs, state-of-the-art SWE-bench scores—then disappeared before most teams finished evaluating it. Opus 4.8 remains the best generally available Claude model; watch Anthropic's status page for restoration rather than building production dependencies on a model ID that may stay dark for weeks.