The Government Pulled Anthropic's Two Best Models. Here Is What Still Works.

Fable 5 and Mythos 5 went dark three days after launch under a federal export-control order. Opus 4.8 still runs every job you care about, and the real lesson is about not betting a workflow on one model.

What You Will Learn

• Exactly what the June 12 export-control directive said and why it forced a full shutdown of both Mythos-class models.
• Which Anthropic models stayed online (Opus 4.8, Sonnet 4.6) and what each one is best for right now.
• How to move long-document work off Fable 5 and onto Opus 4.8 without losing accuracy.
• A side-by-side comparison of Fable 5 (suspended) and Opus 4.8 (available) so you can pick the right fallback.
• The concentration-risk lesson every executive should bank before the next outage.

On Tuesday, June 9, 2026, Anthropic shipped Claude Fable 5, its first Mythos-class model built for general use. A 1M-token context window. The kind of very long, autonomous work that lets one model read an entire data room or chew through a quarter of contracts in a single pass. Teams started routing their heaviest jobs to it within hours.

By Friday at 5:21 PM ET, it was gone. Anthropic received a US export-control directive citing national security authorities, signed by Commerce Secretary Howard Lutnick and sent to CEO Dario Amodei. The order requires suspending all access to Fable 5 and Mythos 5 for any foreign national, inside or outside the US, including Anthropic's own foreign-national employees. Because there is no way to filter foreign nationals from US users in real time, Anthropic disabled both models for everyone to stay compliant.

This is the first time the US government has pulled a commercial frontier model from the market. If you stood up a workflow on Fable 5 this week, it stopped working three days after you built it. That is the whiplash. The good news is that the rest of the Anthropic lineup never went down, and the fix is mostly a routing change you can make today.

This is a PromptHacker Premium deep dive.

Below the gate: the exact Opus 4.8 batching and citation moves to keep your long-document jobs running, plus the concentration-risk checklist.

What Actually Happened, in Plain Terms

The directive is an export-control action. It treats access to Fable 5 and Mythos 5 as something that cannot be handed to a foreign national, the way certain hardware and software cannot be exported without a license. The letter cited national security authorities and arrived at 5:21 PM ET on June 12.

The scope is what makes it sweeping. It does not just block users in other countries. It blocks any foreign national, wherever they sit, including foreign nationals on Anthropic's own payroll. A US-based engineer who is not a US citizen falls inside the order. So does a contractor logging in from a coworking space in another time zone.

That is why the shutdown was total rather than targeted. Anthropic cannot reliably separate a foreign national from a US user at the moment of a request. Faced with a compliance line it could not draw cleanly, it pulled both Mythos-class models for everyone. Anthropic has said it believes the order rests on a misunderstanding and is working to restore access as soon as possible. The primary source is anthropic.com/news/fable-mythos-access, with coverage from 9to5Mac, Quartz, and MarkTechPost on June 12 and 13.

What Still Works

Only the two Mythos-class models went offline. Every other Anthropic model stayed up and unaffected: Opus 4.8, Sonnet 4.6, and the rest of the lineup. If your work runs on those, nothing changed for you. If it ran on Fable 5, Opus 4.8 is the model to move to.

The one real difference is context window. Fable 5 read up to 1M tokens in a single pass. Opus 4.8 has a smaller window, so a document that fit in one Fable 5 call may need to be split into batches. The trade is the only thing you have to engineer around.

Plain-English takeaway: nothing you do every week broke. Opus 4.8 runs the jobs that matter. The only thing Fable 5 gave you that Opus 4.8 does not is reading a giant document in one pass, and you solve that by splitting the document into batches.

How to Move Your Jobs Back to Opus 4.8

Start by splitting any input that exceeded Opus 4.8's window into ordered chunks, then summarize each chunk and feed the summaries into a final pass. For a 400-page filing, that might mean ten chunks of roughly 40 pages each, a short structured summary of every chunk, and one closing call that reasons across all ten summaries. You keep the depth, you just stage it.

Force citations as you batch. Tell Opus 4.8 to quote the exact clause, page, or section behind every claim so you can trace any conclusion back to the source document. Citations matter more once a job is split, because a fact pulled in chunk three needs to survive into the final summary without drifting.

If you want a worked example of Opus 4.8 reading dense legal text and citing as it goes, the Pro Tip on comparing two contracts in 15 minutes (linked below) walks the batching and citation pattern step by step. The same structure carries over to filings, RFPs, and board packets.

The Real Lesson: Concentration Risk

The deeper takeaway has nothing to do with Anthropic and everything to do with how you build. A workflow that runs on exactly one model is a workflow with a single point of failure. This week that failure came from a federal order. Next time it could be a price change, a rate limit, a deprecation, or an outage. The cause does not matter to the team whose job stopped working.

The teams that barely felt June 12 were the ones who already had a second model qualified. They had tested their prompts against an alternative, knew where output quality shifted, and could flip a routing flag instead of rebuilding under pressure. Qualifying a backup is cheap when nothing is broken and expensive when everything is.

For any workflow you would call critical, treat a second model as a requirement, not a nice-to-have. Keep it tested, keep it warm, and document the trade-offs (context window, speed, cost) so the switch is a decision you have already made rather than one you scramble to make at 5:21 on a Friday.

Action Steps Summary

• Stop routing new work to Fable 5 or Mythos 5. Both are offline under a federal export-control order, with no confirmed restore date.
• Move long-document jobs to Opus 4.8. It stayed online and handles the reasoning work; the only change is staging large inputs.
• Batch anything that exceeded the window. Split into ordered chunks, summarize each, then run one closing pass across the summaries.
• Force citations on every batched claim. Make Opus 4.8 quote the exact clause or page so conclusions stay traceable across chunks.
• Qualify a second model for every critical workflow. Test it, keep it warm, and document the trade-offs so the next outage is a flag flip, not a rebuild.