Claude Fable 5 Weekly Limit (2026): Reset, Cap, Opus 4.8

The Claude Fable 5 weekly limit is not a separate bucket you can look up on a pricing page — it is a share of the weekly usage limit your plan already has. On Max and premium seats you can spend up to 50% of that weekly limit on Fable at no extra cost; on Pro and standard Team seats you get no Fable allowance at all and the model bills to usage credits from the first message. That single split explains almost every question in this cluster, including the one that sends most people here: the Claude Code error "Usage credits are required for this model."

Since July 20, 2026, Pro and standard Team users have been meeting that credits prompt, because Fable stopped being free-in-plan on July 19, 2026 at 11:59:59 PM PT. Max users who should not have seen it saw it too for a while, which is where the bug reports come from.

Three unrelated things get filed under the same search phrase, and telling them apart is the difference between a two-minute fix and a support ticket:

• The weekly limit and the billing gate. Fable draws on plan limits on Max and premium seats, and on usage credits on Pro and standard Team seats. Expected behavior, not an outage.
• The safety fallback. A classifier can reroute a Fable request to an Opus model mid-conversation. A content mechanism, not a billing one.
• The July 17, 2026 outage. A real Anthropic incident in which Fable wrongly demanded credits for about an hour, confirmed on the status page.

Everything below is anchored to Anthropic's Fable plan help article, its usage-credits and limit-reset articles, the Claude Code model configuration and costs docs, the changelog, and the public bug reports. Where a source prints no number, we say so instead of guessing.

Quick answer

• What the Fable 5 weekly limit is: on Max, premium Team seats, and premium legacy Enterprise seats, up to 50% of your weekly usage limit can go to Fable at no extra cost. It is a share, not a bonus pool.
• When it resets: session limits reset every five hours; weekly limits reset on their usual day and time. Eligible plans sometimes get a limit reset you trigger yourself from Settings > Usage.
• What happens at the cap: you "can keep using Fable models with usage credits, or switch to another model." If you hit the plan-wide "You've hit your weekly limit", switching models does not help — that window is shared across all models.
• On Pro and standard Team seats: no Fable allowance at all; the model runs on usage credits from the first message, which is why Claude Code shows "Requires usage credits" on the Fable row.
• Fable 5 vs Opus 4.8: Fable is $10/$50 per million tokens against Opus 4.8's $5/$25, and Opus 4.8 is the documented fallback target for cybersecurity-flagged Fable requests. Full table below.

How the Claude Fable 5 weekly limit works

Anthropic's plan article draws the line by plan and seat tier, and the whole cluster follows from it:

• Max plans, premium Team seats, and premium seats on legacy seat-based Enterprise plans: Fable 5 and Fable 5.1 "are included as a standard part of your plan. You can use up to 50% of your weekly usage limits on Fable models at no extra cost." They draw from your regular weekly limits and "use them faster than other Claude models."
• Pro plans and standard Team seats: Fable 5 and Fable 5.1 "aren't included in your plan's usage limits. You can use them with usage credits." Eligible Pro and Team standard seats got a one-time promotional credit when Fable 5 moved to credits in July 2026; it covered Fable 5 only, with no equivalent for Fable 5.1.
• Standard seats on seat-based Enterprise plans: not included either; usable only if your organization has enabled usage credits.
• Usage-based Enterprise plans and the Claude API: billed at standard API rates.

The 50% rule is a share, not extra headroom

Two consequences follow directly from Anthropic's FAQ. First, it is a share, not a bonus pool. Asked whether Max gets 50% more weekly limit for Fable, the article answers: "No. You can use up to 50% of your weekly limit on Fable models, but your use of other models draws from the same usage limits and you can never use more than your weekly limit." A heavy Fable week eats your Opus headroom too.

Second, Fable burns limits faster than Opus. The plan article says Fable models "use them faster than other Claude models," so a handful of long agentic sessions can consume that half quickly. The practical planning number — how many tokens that 50% equals — is not published by Anthropic for Fable specifically, and we are not going to invent one; measure it in /usage on your own account instead.

When the Fable 5 weekly limit resets

Reset mechanics differ by plan, which is where most "the limit is lying" complaints come from:

• Session windows: Anthropic's usage-credits article says "Your plan's included usage limit will reset every five hours once you reach it. Usage credits don't affect this reset timing."
• Weekly windows: they reset on their usual day and time. Team and Enterprise seat allowances reset on "a rolling five-hour window and a weekly window," shared with Claude chat and Cowork, per the costs docs.
• On-demand resets: eligible plans sometimes receive a limit reset you trigger from Settings > Usage → Resets → Reset for free. Anthropic notes the button "isn't currently available on Claude Mobile or in Claude Code in your terminal or IDE," and that weekly limits still reset on their usual day and time.

What happens when you hit the cap

Anthropic spells out both endings. On Max and premium seats, once you have used up to 50% of your weekly limits on Fable, you "can keep using Fable models with usage credits, or switch to another model to keep working within your plan's usage limits."

Which of those works depends on which message you got, and the costs docs are precise about it:

• "You've hit your weekly limit" (or your session limit) is a seat-based window "shared across all models, so the developer can't restore access by switching models with /model. The message shows when the window resets."
• "You've hit your Opus limit" / "You've hit your Sonnet limit" are model-family windows; after those, switching to a model outside that family does keep you working.
• Claude Code v2.1.234 and later can also wait and continue the interrupted task after the reset; /rate-limit-options is the manual entry point.

Seeing the Fable weekly meter

/usage shows plan usage bars and a usage-credits row. One sharp edge was closed in the 2.1.283 changelog: "Fixed the weekly Fable limit not appearing in /usage and the VS Code usage meters when telemetry is disabled." If your Fable weekly bar was invisible, that version is the fix. Note that /usage is also where you confirm a genuine bug: several open reports describe the credits gate firing while the weekly meter shows headroom — issue #79413 on Pro, issue #80484 on a /model switch, and a Max-plan report from July 20, 2026, the day the new rules took effect (issue #79337). Those are user reports in the public tracker, not Anthropic statements; the correct reading is "update, check plan, then add to a report," not "the limits are fake."

What "usage credits are required for this model" actually means

This is the diagnosis for the error string, and it is the direct consequence of the split above. On Pro and standard Team seats, Fable is not in your plan's limits, so Claude Code gates it behind credits. The model configuration docs put it plainly: "When it does, the /model picker shows 'Requires usage credits' on the Fable row."

The switchover date is exact. Anthropic states in the plan article: "We previously ran a promotion that allowed you to use up to 50% of your weekly subscription limit on Claude Fable 5 at no extra cost. That promotion ended on July 19, 2026 at 11:59:59 PM PT, and it applied to Fable 5 only. Claude Fable 5.1 was never part of it." The next day, Pro users started meeting the credits gate — and so did some Max users who should not have.

Version matters too. The plan article says Fable 5 needs Claude Code 2.1.170 or later and Fable 5.1 needs 2.1.255 or later; the model-config page separately says Fable 5.1 requires v2.1.257 or later. The two official pages disagree by two patch versions — run claude update and both floors are satisfied. (The fable alias also resolves to Fable 5.1, not Fable 5, unless ANTHROPIC_DEFAULT_FABLE_MODEL overrides it.)

The fastest fix, step by step

1. Confirm your plan and seat tier first. If you are on Pro or a standard Team seat, the gate is expected and no amount of relaunching changes it. If you are on Max or a premium seat and still see it, treat it as a bug and check your version before anything else.
2. Update Claude Code. Run claude --version, then claude update (or npm install -g @anthropic-ai/claude-code@latest). Two of the ugliest edges were fixed in the 2.1.282 changelog: /model with a full Fable model id used to stop at an API error instead of opening the usage-credits prompt, and an unanswered Fable credit prompt could switch models in SDK-hosted sessions such as Claude Desktop.
3. Open /model and read the Fable row. Three states, three different problems: the row says "Requires usage credits" (billing — you are in the right place); the row is missing (version too old, you are on Free, or your organization has not enabled Fable); the row is greyed out with a note (your organization's availableModels or deniedModels managed settings exclude it — those two settings were added in the 2.1.283 changelog).
4. Choose credits or a different model.
   • To continue on Fable with credits: an interactive session shows a consent prompt before the request bills credits. Accept it and, per the docs, "Claude Code doesn't show the prompt again."
   • To turn credits on: run /usage-credits, which opens Settings > Usage for Pro and Max, or Admin settings > Usage for Team and Enterprise members with billing access. Click Enable in the Usage credits section, set a monthly spend limit, and prepay with Add funds. Credits bill at standard API rates, and the command needs a claude.ai subscription sign-in via /login — not API key authentication.
   • To switch instead: /model opus puts you on the current Opus alias, and your Fable request never touches credits.
5. Check automation before blaming the CLI. In non-interactive mode with -p and through the Agent SDK, the docs state Claude Code "never shows the consent prompt. When a Fable request there would bill to usage credits, Claude Code bills it without asking." If a CI job drained your credit balance, that clause is why — cap it with a monthly spend limit.
6. Know what an unanswered prompt does. With Remote Control connected, in a background session, or in a teammate's session, Claude Code holds the prompt for the dialogExpiry deadline — five minutes by default. If nobody answers, the turn ends without sending the request, a notice lands in the transcript, and your model selection is unchanged. Community reports describe prompts that auto-cancelled without ever being displayed (issue #87832); if that is you, update first and treat a persisting prompt as an open report.

Why your session switched to Opus (it is not the credits bug)

A Fable session that suddenly answers as an Opus model has not hit a billing wall. Claude Code runs safety classifiers on Fable models, Opus 5.5, and Opus 5, and most flags are cybersecurity or biology content. Per the model-config docs, the reroute targets are specific:

• Fable 5.1, Fable 5, and Opus 5.5: biology-flagged requests re-run on Opus 5, and cybersecurity-flagged requests re-run on Opus 4.8.
• Opus 5: cybersecurity-flagged requests re-run on Opus 4.8; biology-flagged requests end in a refusal instead, because Opus 5 has its own biology classifiers and no fallback model.

Anthropic's help article on why Claude switched models confirms automatic switching is on by default and that "the model picker stays on Opus for the rest of the conversation." Switch back with /model, though the same classifier can trip again if the flagged content is still in context. To be asked instead of switched, turn off Switch models when a message is flagged in /config, or set switchModelsOnFlag to false. Fallback requests bill at the fallback model's rates, with a credit for the cache miss.

Fable 5 vs Opus 4.8: a real comparison

Here is the comparison table, with prices from Anthropic's model pricing page and specs from the models overview. Opus 4.8 shipped on May 28, 2026 at $5/$25 per million tokens, per Anthropic's launch announcement.

Two practical reads. Fable costs twice Opus 4.8 per token on input and output, so the premium is only worth it on long, multi-file, genuinely hard sessions; routine edits favor Opus. And the opus alias no longer points at Opus 4.8 — it resolves to Opus 5.5 today, to Opus 5 before v2.1.280, and to Opus 4.8 before v2.1.219. Pin claude-opus-4-8 explicitly if you want that version; our Claude Code default model walkthrough covers the alias change end to end.

FAQ

What is the Fable 5 weekly limit on Max? On Max, premium Team seats, and premium Enterprise seats, Fable can consume up to 50% of your weekly usage limit at no extra cost. It is not an extra 50% of headroom: Anthropic's FAQ says your other models "draw from the same usage limits and you can never use more than your weekly limit." Past the Fable share, you either continue on usage credits or switch models.

When does the Claude Fable 5 weekly limit reset? Weekly limits reset on their usual day and time, per Anthropic's limit-reset article. Five-hour session limits reset once you reach them, and usage credits do not change that timing. Some plans also receive an on-demand limit reset you can trigger from Settings > Usage → Resets → Reset for free; the button is not available in mobile Claude or in the terminal/IDE Claude Code.

Why does Claude Code say "usage credits are required for this model"? Because Fable is not part of the included plan limits on your plan or seat tier. On Pro plans and standard Team seats, Anthropic's plan article says Fable 5 and Fable 5.1 "aren't included in your plan's usage limits. You can use them with usage credits." The /model picker shows "Requires usage credits" on the Fable row, and the string appears in community bug reports such as "Anthropic API Error: Usage credits are required for this model".

How do I fix Claude Code Fable 5 usage credits? Run claude update, then /model, and pick a path. To pay per use, accept the consent prompt in an interactive session, or enable credits with /usage-credits → Settings > Usage → Usage credits → Enable and prepay. To avoid credits, run /model opus and stay inside your plan limits.

Why is Claude Fable 5 not available in my /model picker? Anthropic's checklist is short: a paid plan (Fable is not on Free), a new enough Claude Code version (2.1.170+ for Fable 5; 2.1.255+ or 2.1.257+ for Fable 5.1, depending on which official page you read), and an organization that has not disabled Fable. The 2.1.283 changelog added availableModelsMatch: "exact" and deniedModels managed settings for that last case; when your organization blocks Fable, the row stays in the picker greyed out with a note on why.

Is Fable 5 better than Opus 4.8 in Claude Code? Different tools at different prices: Fable 5 and Fable 5.1 are $10/$50 per million tokens versus Opus 4.8's $5/$25, and Anthropic positions Fable for "demanding reasoning and long-horizon agentic work." Opus 4.8 is the cheaper generalist — and the documented fallback target for cybersecurity-flagged Fable requests. Run Opus for day-to-day edits; reach for Fable when a session is long, multi-file, and genuinely hard.

Was there an Anthropic outage around this error in July 2026? Yes, on July 17, 2026. The status page incident "Elevated errors across Fable 5" affected claude.ai, the Claude API, Claude Code, and Claude Cowork. Anthropic posted that it "applied a fix to resolve the erroneous requirement for usage credits on Fable 5" at 18:48 UTC, and marked the incident resolved at 19:43 UTC the same day. An Ask HN thread — "Did Fable disappear from your Claude usage and requires credits now?" — and Hindustan Times coverage tracked the same window. If your error predates July 20 or came with a status-page banner, that outage — not your plan — was the cause. We could not verify a specific r/ClaudeAI thread for the incident, so treat that particular citation as unconfirmed.

Related reading

• Claude Code insights tutorial — read your own usage patterns before blaming the limit
• Claude Code sandbox tutorial — the permission and sandbox setup worth finishing before a long Fable run
• Claude Code default model — how the opus and fable aliases changed, and how to pin a version
• Claude Code attribution — the same month's other Claude Code governance story
• GLM Coding Plan guide — a cheaper subscription route when credits run out
• Codex CLI tutorial — the same error-rescue workflow on OpenAI's agent