Fable 5 Is Back — Included in Your Plan Until July 7. Don't Waste the Window.

On June 12, I published my first-week roundup of Claude Fable 5. The model went offline the same day.

Today it came back. Anthropic redeployed Fable 5 globally this morning — Claude.ai, Claude Code, the API, Cowork — with a hardened safety classifier and an unusual deal attached: if you're on a Pro, Max, Team, or premium Enterprise plan, Fable 5 is included in your subscription at up to 50% of your weekly usage limits through July 7. After that, it moves to usage credits — metered, on top of your plan.

That's a six-day window to run the most capable generally available model on the planet without a separate bill. Before you burn it on routine work, it's worth understanding what actually happened, because the story behind the outage is more interesting than the outage itself.

What Happened: The Three-Week Gap

The short version, pieced together from Anthropic's redeployment post and The Hacker News' timeline:

June 12 — Amazon researchers found a prompt technique that bypassed Fable 5's cyber safeguards. The exploit got the model to flag software vulnerabilities and, in one case, write code demonstrating how a flaw could be abused. The U.S. Commerce Department responded with emergency export controls requiring Anthropic to restrict Fable 5 and Mythos 5 from "any foreign national, inside or outside the United States" — including Anthropic's own non-citizen employees. Real-time nationality verification being impossible, Anthropic pulled both models for everyone.

June 26 — Mythos 5 access was partially restored to roughly 100 U.S. companies and federal agencies defending critical infrastructure.

June 30 — The Commerce Department lifted the controls after review. Security leaders had signed an open letter calling for removal; one researcher described the reversal as "the government conceding it had gone too far."

July 1 — Fable 5 redeployed worldwide.

Worth noting: Anthropic's own assessment downplayed the exploit's severity, pointing out that identical requests succeed against weaker models — including their own Opus 4.8 and OpenAI's GPT-5.5. The export control wasn't triggered by what the jailbreak produced. It was triggered by what it proved: that the safeguards separating Mythos-class capability from general availability could be bypassed at all.

What It Means

Three things changed while the model was gone, and all three matter more than the outage.

The classifier got a bigger safety margin — and you will feel it. Anthropic says the new classifier blocks the reported technique in over 99% of attempts. It also says, plainly, that the larger margin increases false positives on routine coding tasks. If you do security-adjacent work — the audience of half this blog — the advice I gave at launch is now doubly true: benign vulnerability analysis, defensive tooling, and security research will trip the classifier more often than before. Plan for it.

Blocked requests now reroute instead of dying. On Claude's consumer surfaces, a flagged Fable 5 request automatically falls back to Opus 4.8 with a notification. On the API, fallbacks remain opt-in — the fallbacks parameter with server-side-fallback beta routes a refusal to Opus 4.8 inside the same call, with the declined attempt unbilled. If your Fable 5 integration doesn't set it, a false positive is a dead request. Set it.

A precedent got set. This was the first time the U.S. government pulled a frontier model off the market, and the terms of its return tell you how the next one goes: Anthropic committed to pre-release government access and independent evaluation, rapid information-sharing on jailbreaks, dedicated joint security research teams, and work on shared industry standards. Whatever you think of the three-week ban, "frontier capability ships after government evaluation" is now the operating reality — formalizing what Project Glasswing already hinted at.

What You Should Do Right Now

The window is today through July 7. Six days. Here's the checklist:

1. Check what you actually have. Pro, Max, Team, and premium Enterprise seats get Fable 5 included at up to 50% of weekly usage limits. Standard Enterprise seats get nothing included — an admin has to enable usage credits or your users simply won't see the model. Anthropic hasn't published what "50% of weekly limits" converts to in tokens or messages, so watch your usage dashboard rather than assuming.

2. Front-load your hardest problems. The consistent lesson from early access: teams that got the most out of Fable 5 gave it their hardest unsolved problems first, not their routine work. You have six days of included access to a model whose entire value proposition is the band of tasks nothing else can finish. Spend the window there. Sonnet 5 exists for everything else — I made that case yesterday.

3. API users: re-enable and add fallbacks. If you built on Fable 5 in the June 9–12 window, your integration has been erroring for three weeks. It works again as of this morning — same claude-fable-5 model ID, same $10/$50 pricing, same 30-day data retention requirement. Add the server-side fallback to Opus 4.8 before the tightened classifier finds your edge cases for you. Cloud platforms (AWS, Google Cloud, Microsoft Foundry) are being re-enabled separately, so check your provider's status before assuming an outage is on your end.

4. Decide your post-July 7 tiering now. After the window, Fable 5 on subscription plans goes to usage credits, and the credit-to-dollar conversion hasn't been disclosed yet. The sane default: Fable 5 for planning, architecture, and the genuinely hard 5% ­— Sonnet 5 for bulk production work at a fifth the per-token cost. Cheapest model that clears the quality bar, every time.

Fun Use Cases for the Window

You have six days of Mythos-class capability included in a consumer subscription. The first week of Fable 5 produced a $4 GitHub clone and people beating Pokémon with vision alone. In that spirit — things worth trying before July 7 that you'd hesitate to pay metered rates for:

• The overnight run. Fable 5's signature trick is running autonomously for hours without falling apart. Pick the refactor you've been avoiding for a year — the test suite migration, the framework upgrade, the "we'll fix the types later" debt — write the full spec in one message, start it before bed, and review a finished branch over coffee. The full-spec-up-front part matters: this model rewards well-specified goals and punishes drip-fed instructions.

• Codebase archaeology. Point it at your oldest, weirdest repo — the one where the original author left and the comments lie — and ask for a full forensic writeup: what it actually does, where the bodies are buried, what a modernization plan looks like. The 1M-token context window means a medium-sized codebase fits in one request.

• The game-engine test. Week one's party trick was building playable game engines in days. Give it a one-paragraph game concept and let it run: engine, assets, playable build. Useless? Mostly. But nothing calibrates your intuition for what "long-horizon agentic" means faster than watching a model ship a working game while you watch.

• Sub-agent orchestration. Fable 5 is the first model where parallel sub-agents are genuinely dependable — it sustains async communication with long-running workers instead of losing the plot. Take a task that fans out (audit every dependency, review every open PR, document every service) and let it delegate. This is the pattern that will matter most in production later; the window is a free rehearsal.

• The "scope my hardest problem" session. Even if you don't let it execute, one high-effort planning session on your gnarliest unsolved problem — have it interrogate you, scope the work, and produce the attack plan — is the single highest-value hour you can spend with this model. Take the plan, hand the execution to Sonnet 5, and you've extracted most of Fable 5's value at a fraction of its future cost.

The Verdict

The outage was a milestone dressed as an inconvenience: the first government-ordered frontier model withdrawal, resolved in under three weeks, returning with tighter safeguards and a formal government-evaluation pipeline behind it. That's the durable story.

The actionable story is simpler. The most capable model you can legally use is included in your plan until July 7, and after that it's a line item. Use the week the way the early-access teams did — hardest problems first — and let the metered era find you already knowing exactly what Fable 5 is worth to you.