The Permission Tier: Claude Fable 5 Comes Back Changed

I wrote a few days ago that Opus 4.8 had become the expensive middle: squeezed by a cheaper Sonnet from below and a smarter tier from above. That post treated the top of the stack as a pricing question. This week made it something stranger. The top of the stack turned out to be a permission question, and the permission was briefly revoked for the entire planet.

Fable 5 is back. What came back, exactly, is the interesting part.

Nineteen days at the border

The timeline reads like fiction. June 9: Anthropic ships Claude Fable 5, and it debuts as the clear frontier leader, about five points ahead of any other lab’s best on Artificial Analysis’s index. June 12: the US Commerce Secretary orders Anthropic to cut off access for all foreign nationals, inside or outside the US, including Anthropic’s own foreign-national employees. Since nobody can verify nationality in real time, Anthropic pulls the model for everyone instead. June 30: the controls are lifted. July 1: Fable returns.

The stated trigger, on the record from the White House AI adviser:

A highly credible trusted partner of both Anthropic and the USG who was testing Fable came forward with a jailbreak.

— David Sacks, White House AI adviser

The partner is reportedly Amazon, though nobody has confirmed that on the record. Anthropic publicly disputed the severity, saying the demonstrated capability “is available from other publicly deployed models.” It complied anyway. Whether that was genuine national-security caution or a flex of legal authority that may not even cover model access is still being argued by people better qualified than me.

What’s not in dispute: for nineteen days, the most capable AI on earth was something you needed the right passport to touch. And its sibling still is. Mythos 5, the same model without the safety layer, remains restricted to approved US organizations. One widely-upvoted r/ClaudeAI comment called the shape of it early: the public gets Fable back only after government and corporate partners have moved on to something better. Cynical, unproven, and entirely plausible as a durable arrangement.

What came back

Fable’s return isn’t a clean restore from backup, and Anthropic says so itself. The redeployment announcement is specific about two changes: a new safety classifier that blocks the reported jailbreak technique “in over 99% of cases,” and a fallback where flagged requests get rerouted to Opus 4.8. You get notified, but the answer you receive comes from a weaker model. A few returning subscribers also reported being prompted to upload ID; the announcement says nothing about identity checks, and plenty of users (me included) saw no such prompt. Whatever that check is, it’s undocumented too.

Here’s the sentence that matters, though, and it’s one Anthropic never wrote: the underlying model is unchanged. The announcement asserts what changed and stays silent on what didn’t. No updated system card. No before-and-after capability table. The question everyone is asking, “did it come back dumber?”, is answered by omission.

Just please be the same as when it first came out

— r/ClaudeAI, top comment on the return announcement

That plea got 714 upvotes. The second-most-upvoted take was drier: “Welcome Opus 4.8 back.”

The audit that didn’t happen

The community reached its verdict before it had access. The return thread’s own moderator summary named the number one fear: getting back “a nerfed, lobotomized version of the model we loved.” One user posted “is it just me or is Fable 5 dumber now” as a joke about getting in first.

So you’d expect the independent benchmarks to settle this. They haven’t, and the way they haven’t is the most instructive part of the whole episode:

• The outfit that promised the audit got distracted by the toy. BridgeBench publicly committed, mid-suspension, to rerunning every benchmark the moment access returned: “If the returning Fable 5 scores lower than the original, you will see it here first.” On return day, the same account posted: “FABLE 5 IS SO BACK. I created Minecraft in a single shot.”
• The big boards haven’t re-tested. LMArena’s changelog shows Fable added June 10 and nothing since. Artificial Analysis still displays the launch-day score.
• As of publishing, no one has put pre-suspension and post-return numbers side by side. Not the vendor, not the leaderboards, not the self-appointed watchdogs.

Which means both camps are running on faith. “It feels dumber” is unfalsifiable vibes. But “it’s the same model” is equally unverified, and only one of the two parties had the data to settle it.

The tier you can’t subscribe to

The expensive middle was a story about money: which intelligence you can afford. This is a story about standing: which intelligence you’re allowed. No pricing page lists “US Commerce Department discretion” as a dependency, but everything built on Fable inherited exactly that for nineteen days. One developer put the darker version bluntly: we’re entering an era where you can’t rely on American models, because the intelligence can be dialed down or switched off by decisions made far above your subscription tier.

And when the tap turns back on, you take what flows out of it. The model returns, the meter resets, the benchmarks stay un-rerun, and the only entity that could prove continuity chooses not to. You are not a customer of a product at the frontier. You are a licensee of a capability, revocable at the border, alterable in transit, verified by vibes.

The lesson I’d actually act on: treat frontier-model dependency the way you treat any single-supplier risk. The plan-with-the-brain, execute-with-the-fleet split quietly assumed the brain would always be there. It won’t. Have a fallback chain that you’ve genuinely tested, watch for silent reroutes in your own traces, and keep your own tiny eval suite so “did it change?” is a question you can answer yourself in twenty minutes. The vendors have shown you exactly how much proof of sameness they’ll volunteer: none.

Update: day one on the meter

A few hours of actual use later, the abstract “50% of weekly limits” turned concrete. My own meters, late morning of day one on the 20x Max plan, on a moderate mix of Opus and Fable: session limit fully consumed, the dedicated Fable weekly meter at 29%, all-models at 20%. Extrapolate a normal working week and the cap is gone in about two days. I got lucky, with my weekly reset landing tomorrow; others noticed the same lottery from the losing side: “people whose weekly limit resets in a few days get two full weekly windows… we don’t benefit anything from it.”

The day-one megathread on r/ClaudeAI reads the same everywhere:

• Max 20x: hit the 5-hour cap “in 50 minutes,” which was also “40% of my weekly fable limit.”
• Max 5x: 15 to 20 minutes of coding went “from 0% to 100% of the 5 hour limit, and 20% of the fable limit. That’s insane.” Another user watched a single /code-review consume “my entire 5x Usage” in two minutes.
• Pro, with paid top-up: “Fable-high ate not only my 5-hour Pro allotment, but $30 of the $50 very quickly.”
• The thread’s own auto-generated summary: “it eats your usage limit for breakfast.”

(In fairness, Anthropic reset everyone’s counters a few hours into the relaunch, which muddies some early numbers. The reports above that landed after the reset tell the same story.)

The sharpest arithmetic came from X: the June window gave full quota at roughly double-Opus burn, effectively half a week of work. This window gives a 50% cap at the same burn: “this time we really only have 25%.” And the classifier reroute described above turns out to be a meter problem too, not just a quality one: a blocked request completes on Opus and still bills, and switching back to Fable re-caches the whole conversation and bills again, spending allowance with no new work to show for it.

The adaptations arrived within hours: developers routing Fable to orchestration and review only, with cheaper subagents at high effort doing everything else, plus “make Fable last 10x longer” guides. The permission tier and the expensive middle merged in a single day. What you’re allowed is no longer a yes or a no. It’s a percentage, draining in real time, on its own labelled meter.