Claude Code setup-token sessions wrongly show Fable 5 as usage-credits gated
PawlDani · ghdev · 2026-07-20
What happened
Claude Code users authenticated with a long-lived claude setup-token are being shown a usage-credits upsell dialog when selecting Fable 5, even on Max plans where the model is supposed to remain included.
Evidence
- GET /api/oauth/usage returns 403 because the token lacks user:profile
- GET /api/oauth/claudecli/roles returns 403 for the same reason
- GET /api/oauth/profile also returns 403
- Yet a direct POST /v1/messages with model: claude-fable-5 succeeds using the same token
Root cause
The issue appears to be that setup-token sessions only have user:inference scope, so the client cannot read entitlement endpoints and falls back to the usage-credits prompt.
Workaround
Interactive /login sessions work; minting a fresh setup-token does not fix it.
More from coding & agent
- Codex tip: use Sol with Astra and Luna sub-agents to save usage — pvncher · 2026-09-11
- agents-best-practices: a provider-neutral Agent Skill for designing and auditing agentic harnesses — tom_doerr · 2026-09-11
- Cognition's SWE-2 uses a KKT duality argument in RL to shift the effort Pareto curve — YouJiacheng · 2026-09-11
- First-ever Three.js Conference lands in Paris, with a panel on AI-shortened design workflows — OdinLovis · 2026-09-11
- Data engineering, not agent frameworks, is the real bottleneck for enterprise AI agents — dhruv2038 · 2026-09-11
- RTK Terminal Compression Cuts Tokens but Leaves Your AI Coding Bill Unchanged — Bartaseth · 2026-09-11