---
title: "Claude Fable 5: The Model We Had for Three Days"
date: "2026-06-25"
author: "Graham"
description: "A retrospective on Claude Fable 5: the astonishing three days of builder demos, the US export-control suspension, and why the demos were the policy argument."
tags: ["AI News", "Power of AI"]
url: "https://powerofai.ca/claude-fable-5-the-model-we-lost"
readTime: "7 min"
---

# Claude Fable 5: The Model We Had for Three Days

Claude Fable 5 launched on June 9, 2026. For about three days it was Anthropic's most capable public model: a Mythos-class model with safety classifiers, reportedly scoring 80.3% on SWE-Bench Pro, priced at $10 per million input tokens and $50 per million output tokens. Then on June 12, according to Anthropic's statement, a US export-control directive forced the company to suspend both Fable 5 and Mythos 5 worldwide. As of late June 2026 they remain offline, with no restoration. This is a retrospective on the short window in between, and it stays close to what was publicly demonstrated and stated at the time.

The point of this piece is simple and a little uncomfortable. The capability that builders found most useful in those three days is the same capability the government decided was too dangerous to leave running. The demos were not a sideshow to the policy fight. The demos were the policy argument. That tension, not any single model, is the real story of 2026.

## Quick picks

- **What it was: Fable 5, the public Mythos-class model.** Anthropic's most capable public model: reported 80.3% on SWE-Bench Pro, $10/$50 per million tokens, with safety classifiers.
- **How long it lasted: About three days.** Launched June 9, 2026. Suspended worldwide June 12 under a US export-control directive, per Anthropic.
- **Why it was pulled: A claimed jailbreak.** Per Anthropic and researchers, the concern essentially amounted to asking the model to read a codebase and fix its flaws.
- **The lesson: Do not build production on a model that can vanish.** A model can be removed by order. Keep fallbacks like Opus 4.8 wired in.

## Three days of demos that did not look like demos

Most model launches produce a wave of polished, slightly suspicious clips. Fable 5 produced something different. Builders were not showing off prompts. They were shipping things that would have taken a small team weeks, and the model was doing the unglamorous middle work on its own.

The clearest example came from a builder posting as @akiraxtwo, who built a Hades-style browser roguelike starting from an empty folder, using Fable 5 and Three.js. The notable part was not the game. It was that the model chose its own free art assets and wrote the asset pipeline to wire them in. That is the part of a project that usually stalls a hobbyist for days, and it was handled as a step, not a feature request.

- A Hades-style browser roguelike built from an empty folder with Fable 5 and Three.js, where the model picked its own free art assets and wrote the asset pipeline (@akiraxtwo).
- "Crysis in Three.js" generated procedurally in basically one shot (@dangreenheck).
- Generative art and explorable universes that came with their own lore and sound (@anshuc, @hive_echo).
- A real small-business automation that watches a city's public pool-permit filings and mails owners a render of their finished backyard (@everestchris6).

## The automation that made it concrete

The roguelike and the procedural Crysis clone were the spectacle. The pool-permit automation, posted by a builder as @everestchris6, was the part that should make any small-business owner pay attention. It watches a city's public pool-permit filings, then mails the owners a render of their finished backyard.

That is not a tech demo. That is a marketing department compressed into a script: data ingestion, filtering, image generation, and outreach, stitched together by one person using one model. It is the kind of workflow that, a year earlier, you would have hired an agency or a small dev shop to build. The model did the integration work that normally eats the budget.

## Then it was gone

On June 12, according to Anthropic's statement, a US export-control directive forced the company to suspend Fable 5 and Mythos 5 worldwide. As of late June 2026, both remain offline with no announced restoration. The government's side has not been laid out in the same public detail, so the account here leans on Anthropic's statement and on security researchers writing publicly.

The stated concern was a jailbreak. But per Anthropic and security researchers, including Simon Willison, the behavior in question essentially amounted to asking the model to read a codebase and fix its flaws. That framing matters, because the same ability has an obvious defensive use. Mozilla reportedly used Mythos to find more than 270 Firefox vulnerabilities. The capability the government treated as the danger is the capability defenders used to make software safer. These descriptions reflect what was reported at the time and remain disputed.

- Per Anthropic: a US export-control directive required suspending Fable 5 and Mythos 5 worldwide around June 12.
- As of late June 2026: both models remain offline, with no restoration announced.
- Per Anthropic and researchers including Simon Willison: the "jailbreak" essentially amounted to asking the model to read a codebase and fix flaws.
- Reported: Mozilla used Mythos to find 270+ Firefox vulnerabilities, the same ability used for defense.

## The demos were the policy argument

Here is the part worth sitting with. Reading a codebase and finding its flaws is exactly what the builders were celebrating. It is what let the model write the asset pipeline, generate the game, and stitch together the pool-permit automation. The same depth of code reasoning that made the demos possible is what the government decided was too dangerous to leave on.

So the demos are not separate from the suspension. They are the evidence on both sides of the same argument. To a builder, "it can read a whole codebase and fix it" is the headline feature. To an export-control reviewer, the same sentence reads as a risk. There is no version of this model that is great at the useful thing and harmless at the dangerous thing, because they are the same thing.

After the suspension, a builder posting as @anshuc spoke for a lot of people: "Someone please give us this class of model again." That is the honest emotional center of this story. People had, briefly, a tool that collapsed the distance between an idea and a working thing, and then it was switched off by order.

## The practical takeaway

The lesson is not that Fable 5 was good or that the suspension was right. It is that a frontier model can now disappear by directive, on a few days' notice, for reasons outside your control. If your product or workflow depended on Fable 5, you found that out the hard way on June 12.

So do not build production on a model that can vanish by order. Treat access to the newest frontier model as a privilege that can be revoked, not a foundation. Keep fallbacks wired in, like Opus 4.8, so that when a model goes away your work does not. The boring engineering of fallbacks is what separates a resilient product from a demo that died on June 12.

- Assume the newest frontier model can be removed with little notice.
- Keep a working fallback model, such as Opus 4.8, in your stack.
- Do not promise a customer a workflow that only runs on one frontier model.
- Save the prompts and pipelines, not just the outputs, so you can re-run them elsewhere.

## Related Power of AI pages

- [Claude Fable 5 and Mythos 5: What Happened](/claude-fable-5-mythos-5): The durable plain-English explainer for the launch and the suspension.
- [The Signal: AI Week, June 25, 2026](/the-signal/ai-week-june-25-2026): The weekly roundup that puts this retrospective in context.
- [Agent Loops](/agent-loops): How long-horizon, codebase-reading work like the Fable 5 demos actually runs.

## Sources and official references

- [Anthropic: Statement on Fable 5 and Mythos 5 access](https://www.anthropic.com/news/fable-mythos-access)
- [Malwarebytes: Claude Fable 5 and Mythos 5 abruptly disabled after US gov deems them too clever](https://www.malwarebytes.com/blog/ai/2026/06/claude-fable-5-and-mythos-5-abruptly-disabled-after-us-gov-deems-them-too-clever)
- [National Law Review: Anthropic suspends access to Fable 5 and Mythos 5](https://natlawreview.com/article/ai-company-anthropic-suspends-access-claude-fable-5-claude-mythos-5-following-us)
- [Simon Willison](https://simonwillison.net/)
- [Demo: Hades-style roguelike (@akiraxtwo)](https://x.com/akiraxtwo/status/2064780732082651402)
- [Demo: Crysis in Three.js (@dangreenheck)](https://x.com/dangreenheck/status/2064586083975745870)
- [Demo: pool-permit backyard automation (@everestchris6)](https://x.com/everestchris6/status/2064746128869138847)
- [Reaction: "give us this class of model again" (@anshuc)](https://x.com/anshuc/status/2065686746852163954)