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
- NVIDIA says Nemotron 3 Ultra hit 97.1% on agentic RTL chip-design tasks — NVIDIAAI · 2026-07-27
- Tokyo Agent Forge hackathon shipped production-ready AI agents in one day — DavidBennett__ · 2026-07-27
- Long-running agents will need immutable event logs, this thread argues — sebpaquet · 2026-07-27
- Agentic Data Science in Practice: Agents Write Code but Answer Wrong Questions — hugobowne · 2026-07-27
- A VS Code extension adds Markdown-style highlighting to Alchemy string templates — samgoodwin89 · 2026-07-27
- Claude’s Stripe MCP connector is being called unusable after repeated disconnects — evielync · 2026-07-27