Some dates are worth putting in your calendar as a Claude user. July 7 is one of them. Because starting July 8, the way you access Fable 5 changes — and if you’re not prepared, you’ll suddenly find yourself without the model.
What’s happening
Fable 5 has been available again since July 1, after 18 days offline under the US export controls. Anthropic wrapped it into subscriptions as a stopgap: for Pro, Max, Team, and select Enterprise plans, Fable 5 is included through July 7 — but capped at 50 percent of your weekly usage limit.
That ends on July 8. From then on, access runs on usage credits billed separately from your regular plan. If you haven’t enabled credits, you lose access to Fable 5. Plain and simple.
Why the cap?
Anthropic describes the 50 percent limit as capacity management. After 18 days of forced downtime, the infrastructure needs to scale back up before the model can return at full strength. The shift to credits after July 7 is explicitly not meant as a permanent price change — Anthropic wants to bring Fable 5 back as a standard subscription feature once capacity allows. The catch: there’s no target date for that.
Who this affects
It hits hardest for anyone who’s been using Fable 5 in the web interface or mobile app since July 1 without any credits on file. For developers on Claude Code or API pipelines, less changes: on the API, Fable 5 was always priced separately — $10 per million input tokens, $50 per million output tokens.
For Enterprise, read the fine print: standard seats get no included Fable 5 allowance, so access only works through credits. Premium seats include Fable 5 through July 7, after which they too need credits enabled.
My take
For most day-to-day tasks, Sonnet 5 remains the smarter pick — it stays in your subscription and runs at introductory pricing through August 31. Fable 5 is the model for the hard cases, not for standard chat.
Still: if you’ve gotten used to Fable 5 over the last few days, check your billing settings today. Otherwise Monday morning is an unpleasant surprise. And honestly, the whole episode shows how fast access to a model can change — first the export ban, then the return, now the credit switch. That’s not what reliability looks like.
Sources: