Fable 5 Was Here for Two Days. Then It Wasn't.

Anthropic shipped Fable 5 on a Monday. By midweek I couldn't use it anymore. Two days. That's the entire window I got with the most capable Claude they'd ever handed the public — and the reason it vanished wasn't even Anthropic's call.

Quick note: I wrote a version of this the day it got pulled, and I did the thing I tell other people not to do — I said there was no verified reason and then guessed. There was a reason. It just hadn't surfaced yet. Here's the corrected version, because getting it wrong quietly isn't the brand.

I wrote about Fable 5 the day it dropped. The capability jump was real — but it shipped with a strange amount of machinery bolted on. At the time I called the restrictions the fine print. Looking back, the restrictions were the tell.

what I was doing with it

I'm not getting into specifics — that's my own work and it stays mine. The short version: I had Fable 5 running inside the kind of agentic setup I build on my own hardware, pushing it on real tasks, the way I test anything I might actually depend on. Two days of that. Enough to start forming an opinion, not enough to finish one. Then the door closed.

a model that shipped already half-locked

Here's what struck me before it ever got pulled: Fable 5 didn't ship like something they wanted loose in the world. It shipped like something they were nervous about. Double the price of Opus 4.8. A safety classifier that automatically handed a slice of your requests to a weaker model. Its stronger sibling, Mythos, walled off to vetted partners. Mandatory 30-day retention with no opt-out, even for people who'd had one.

You don't wrap a launch in that much restraint unless somebody's already worried about what the thing can do. So when it disappeared a couple days later, the surprise wasn't that it happened. The surprise was who pulled the trigger.

what actually happened

Not an internal safety walk-back. Not Anthropic getting cold feet. On June 12, a U.S. government export-control directive forced Fable 5 offline — national-security grounds, tied to a reported jailbreak that could expose the restricted, Mythos-class capability underneath. The government moved, and the strongest public model on the market went dark overnight.

Anthropic's side of it: they've called the order a misunderstanding, apologized for the disruption, and said they're working with the authorities to restore access. The mandatory-retention piece didn't help either — it created real friction with partners trying to deploy it.

As of this week, it's still down. No return date.

Sit with that for a second, because it's the whole point. The thing that took my model away wasn't a price change or a deprecation notice or a company changing its mind. It was a government export action landing in the middle of the week. No warning I could've planned around. No setting I could've flipped.

does it come back?

Probably — but not the same. That's a guess, and I'll label it a guess: probable, not known. My read is it returns more locked down than it launched, which is saying something. More routing to weaker models on the public tier. A smaller real-capability envelope for the rest of us. The genuinely strong version reserved even harder for the partner program. The pattern this whole cycle is consistent — the frontier keeps moving, and the public's access to the actual frontier keeps coming on a longer leash with a tighter collar. Fable 5 going dark for an export order fits that exactly.

the bottom line

I got two days with the best public Claude there's been, and the most useful thing I'm keeping isn't about Fable 5 at all.

It's this: if your work depends on a model you don't own, you don't control that dependency. It can show up Monday and be gone Wednesday — and the thing that takes it away might not even be the company that built it. A government, a contract, a classifier, a policy you never saw. Your only real vote is which fallback you wired up first.

That's not a reason to never build on a frontier model. It's a reason to never build on only one, and to keep a path that's actually yours. I run my own hardware for exactly this. Weeks like this one are why.

— Dru Edwards