[BUG] Fable 5 model-switch dialog says "billed separately from your plan" — contradicts documented plan inclusion

Status Fixed / completed
Maintainer reply None cached
Activity 2 comments · opened Jul 20, 2026 · closed Aug 25, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Environment: Claude Code CLI, Max plan

What happened: Running /model claude-fable-5[1m] (or selecting Fable 5 via the model switcher) shows this confirmation dialog:

Continue on Fable 5 with usage credits?
Fable 5 runs on usage credits, billed separately from your plan. Your other models remain included in your plan.
[Continue with Fable 5] [Switch to the default model and continue]

Expected: Per support.claude.com/en/articles/15424964 (effective 2026-07-20), Fable 5 is included as a standard part of Max/Team Premium/Enterprise Premium plans, at no extra cost for up to 50% of weekly usage limits. Only usage beyond that 50% threshold draws on separate usage credits.

Actual: The dialog unconditionally states Fable "runs on usage credits, billed separately from your plan," with no mention of the included allowance. This reads as if Fable is never plan-covered, which contradicts the documented terms and will likely cause subscribers to avoid a model they're actually entitled to use at no extra cost.

What Should Happen?

Suggested fix: Dialog copy should reflect remaining included Fable quota for the week, and only present the usage-credits framing once that 50% threshold is actually exceeded.

Error Messages/Logs

Steps to Reproduce

change model to fable mid session.

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

latest

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗