Anthropic updates Claude Fable 5 limits with 5-hour and weekly resets

• Anthropic reset Claude Fable 5's 5 hour and weekly quotas on launch day after users including bridgemindai's Max-plan report and theo's usage post said they burned through access in under an hour.
• ClaudeDevs' reset announcement confirmed the reset, and theo's follow-up shows how quickly that change propagated through the launch-day crowd.
• Access depended on the latest clients: ClaudeCodeLog's changelog post says Claude Code 2.1.170 was required for CLI access, while ClaudeDevs' access note told users to run /model claude-fable-5 or update Claude Desktop.
• Anthropic's Claude Fable 5 launch post, echoed by scaling01's pricing summary and dejavucoder's screenshot question, said Fable 5 was included on subscription plans only through June 22, then moved to usage credits.

You can read Anthropic's launch post for the staged rollout language, check the Claude Code 2.1.170 changelog for the client-side gate, and scroll the launch-day posts from bridgemindai's usage screenshot and theo's usage post to see why the reset landed a few hours later.

The reset came after Fable 5's first wave of users reported absurdly fast exhaustion. bridgemindai's post said a $200 per month Claude Max plan hit limits in under 30 minutes, and theo's follow-up put his own remaining usage at roughly an hour.

Anthropic did not spell out new numeric caps in the reset post. What it did say, via ClaudeDevs' wording, is that both the rolling 5 hour bucket and the weekly bucket were manually refreshed on the same day Fable 5 went live.

Anthropic's launch post framed subscription access as a temporary capacity valve:

• From June 9 through June 22, Fable 5 was included on Pro, Max, Team, and seat-based Enterprise plans.
• Starting June 23, using Fable 5 would require usage credits.
• Anthropic said it would extend the included window if capacity allowed, then later restore Fable 5 as a standard subscription feature.

That wording explains why kimmonismus' screenshot showed the in-product message "Fable 5 requires usage credits" even as testingcatalog's post described the model as temporarily included on plans. The free window was real, but it was already being presented as provisional.

Fable 5 was not just a model launch, it was also a client update story.

The access checklist across Anthropic's posts and docs was short:

• Claude Code users needed version 2.1.170, according to ClaudeCodeLog's changelog post and the 2.1.170 changelog.
• If the model selector did not show Fable 5, ClaudeDevs' note told users to run /model claude-fable-5 manually.
• Desktop users were told, again by ClaudeDevs' note, to update to the latest app build.

That combination explains part of the launch-day confusion. Some users were dealing with quotas, others were dealing with stale clients, and both failure modes looked like "I can't use Fable 5."

The same 2.1.170 release that unlocked Fable 5 also fixed a nastier Claude Code bug. According to ClaudeCodeLog's summary and the official changelog, sessions launched from VS Code's integrated terminal, or from shells inheriting Claude Code environment variables, could fail to save transcripts and then disappear from --resume.

That is a separate issue from Fable 5 limits, but it mattered on the same day because the model rollout pushed more users into the CLI. Anthropic shipped the model gate and the resume fix together.