Anthropic fixes Fable 5 selection outage and issues refunds

• Fable 5 access failed for roughly 30 minutes, with ClaudeDevs' resolution post saying users may need to restart Claude Code and reselect Fable with /model.
• The failure mode was an erroneous usage-credit gate while plan quota still appeared available, while peakcooper's screenshot showed Fable 5 failing on Claude Max with 33% session and 34% weekly usage used.
• Affected extra-usage customers get refunds plus matching credits, according to ClaudeDevs' refund note.
• From July 20, Fable 5 becomes a standard 50% allocation for Max and Team Premium, while Pro and Team Standard move to usage credits with a one-time $100 credit, per claudeai's plan update.
• A separate Fable 5 gate remains: QuixiAI's screenshot caught a safeguard-triggered switch to Opus 4.8, and the Claude Help Center says blocked Fable requests can fall back to Opus 4.8.

The Claude Status incident is unusually precise: Anthropic moved from investigating at 18:32 UTC to a fix at 18:48 UTC, then resolution at 19:43 UTC. A Claude Code GitHub issue captured the backend shape of the bug: Fable's meter disappeared and users with subscription allowance still got Usage credits are required for this model. Anthropic's earlier Fable 5 redeployment post explains why the error spooked builders, because Fable 5 had been included across Claude Platform, Claude.ai, Claude Code, and Claude Cowork up to 50% of weekly usage limits before moving to credits.

ClaudeDevs said Fable was not selectable within Claude.ai or Claude Code for a 30 minute period. The same post told users to restart Claude Code and reselect Fable with /model if Fable was no longer their default.

The status page timeline:

• 18:32 UTC: Anthropic opened an investigation into elevated errors across Fable 5.
• 18:36 UTC: Anthropic said users were prevented from selecting Claude Fable 5 in Claude.ai, Claude Code, and other surfaces.
• 18:48 UTC: Anthropic said it had applied a fix for the erroneous usage-credit requirement.
• 19:43 UTC: Anthropic marked the incident resolved and said Fable 5 was available again without usage credits.

The important word on the official status page was "erroneous." The credit wall existed in the product path, fired for the wrong users, then got rolled back.

The visible symptom was more disruptive than a missing model picker entry. In bridgemindai's terminal capture, Claude Code accepted Fable 5 as the default, read a source file, then stopped on Usage credits are required for this model.

Other reports showed the same gate with usage remaining:

• Claude Code Pro: Fable 5 with xhigh effort hit the credit wall after reading a 385-line file, shown in bridgemindai's terminal capture.
• Claude Max: Fable 5 with low effort failed on hello world while the plan UI showed 33% session usage and 34% weekly all-model usage, shown in peakcooper's screenshot.
• /compact: daniel_mac8's screenshot showed compaction failing with the same usage-credit error.
• Claude chat: QuixiAI's screenshot showed a prompt answered only by the credit requirement.

The GitHub bug report described the same mismatch from Claude Code users: active subscription usage remaining, Fable supposedly available until July 19, then a credit prompt and a disappearing Fable usage tracker.

ClaudeDevs said users with extra usage turned on may have been overcharged. Affected users get the charged credits refunded, plus an additional credit equal to the amount charged.

That matched the failure mode mattshumer_ reported: he said he had to purchase credits to keep runs going even though his usage limit was not close to used up.

Anthropic handled the aftermath as a billing correction. That is the part engineers running long agentic sessions will remember.

Anthropic posted the new plan split the next morning:

• Max: Fable 5 included at 50% of limits.
• Team Premium: Fable 5 included at 50% of limits.
• Pro: Fable 5 available via usage credits, with a one-time $100 credit.
• Team Standard: Fable 5 available via usage credits, with a one-time $100 credit.

claudeai said demand for Fable had been difficult to predict, which is why Anthropic had rolled it out to subscription plans in stages and extended access several times while adding capacity. The certainty note said Anthropic was making access standard for the plans that use Fable most intensively.

The outage landed on top of existing quota frustration. HamelHusain said Fable could saturate current session limits and block other subscription models while the weekly all-model counter still had room.

Steve_Yegge described an uglier workaround: Fable mule accounts burning 2% of session limits per minute, with Emacs macros to switch accounts near 95% usage Steve_Yegge's mule-account post.

ClaudeDevs had reset 5-hour and weekly rate limits for all users two days earlier. The reset changed percentages but not timers, according to theo's follow-up, which meant an existing weekly reset could still arrive hours later.

A separate Fable access path showed up after the outage: safeguards can switch the model inside a conversation. QuixiAI's screenshot showed Fable 5 flagging a message and switching the conversation to Opus 4.8.

The Claude Help Center says most Fable queries blocked by safeguards may receive a response from Claude Opus 4.8 instead. The same help article says users can switch back to Fable 5, but repeated blocks can occur because the original request remains in the conversation.