[Blocking] Fable 5 forces usage-credits fallback despite Max plan Fable quota barely used (3%)

Status Open
Maintainer reply None cached
Activity 1 comment · opened Jul 20, 2026

Summary

Fable 5 is refusing to run under my Max 20x plan quota and is instead requiring a separate "usage credits" pool that is already exhausted — even though my Max plan's own weekly Fable allocation is barely touched. This is currently blocking me from using Fable 5 at all.

Details

  • Plan: Max 20x
  • Usage dashboard shows:
  • Current session: 7% used
  • Weekly, all models: 14% used
  • Weekly, Fable 5 specifically: only 3% used
  • The dashboard itself states: "Fable 5 is still included with your Max plan. If you see a prompt to set up usage credits for it, restart Claude Code."
  • I restarted Claude Code as instructed — the problem persisted.
  • The session then auto-switched away from Fable with this message:

Switched to Sonnet 5 for this session · Fable 5 requires usage credits · /model to change

  • Separately, my Usage Credits pool (a distinct pay-as-you-go pool, $75/month limit) is at 99% used, balance -$0.01, auto-reload off, resets Aug 1. This appears to be the pool Fable is incorrectly drawing from instead of the Max weekly Fable quota shown above.

Expected behavior

Fable 5 usage should draw from the Max plan's included Fable weekly allocation (3% used, plenty of room), not from the separate usage-credits pool — consistent with the dashboard's own stated entitlement.

Actual behavior

Fable 5 is gated behind usage credits regardless of remaining Max plan quota, and the documented restart workaround does not resolve it.

Impact

This is currently blocking all Fable 5 usage for me despite having ample plan quota remaining. Requesting priority attention since this looks like an entitlement/billing-logic bug affecting Max plan users broadly, not just an edge case.

Environment

  • Claude Code CLI
  • Plan: Max 20x
  • Model: Fable 5 (claude-fable-5)

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗