[BUG] /model picker shows Fable 5 as disabled while --model claude-fable-5 works on the same account

Open 💬 3 comments Opened Jul 2, 2026 by hanzanwow
  • [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 version: 2.1.198
  • Platform: Anthropic API (Claude Max subscription)
  • OS: Windows 11
  • Terminal: Windows Terminal (PowerShell)

The /model interactive picker marks Fable 5 as unavailable:
Fable (disabled) Claude Fable 5 is currently unavailable. Learn more:
https://www.anthropic.com/news/fable-mythos-access

Selecting it or running /model Fable returns:
Model 'Fable' is not currently available for your account. Claude Fable 5 is currently unavailable.

However, starting a session with claude --model claude-fable-5 on the same machine/account works: the session runs as "Fable 5 with xhigh effort" (1M context) and serves requests normally. The startup banner also confirms entitlement: "Fable 5 is back. Until July 7, you can use up to 50% of your plan's weekly usage limit on Fable 5."

So the server accepts Fable 5 requests, but the picker's client-side availability flag still reports it as disabled — presumably a stale/cached gating flag left over from the June 12 suspension that hasn't been invalidated after the July 1 re-enable.

Picker: disabled. Direct flag: works. Restarting the CLI does not refresh the flag.

What Should Happen?

The /model picker and /model fable should be consistent with server-side entitlement.

Since claude --model claude-fable-5 starts a working Fable 5 session on the same account (confirmed via /status: Model: claude-fable-5), the picker should list Fable as selectable and /model fable should switch to it — or both paths should fail identically.

Error Messages/Logs

The `/model` interactive picker marks Fable 5 as unavailable:
Fable (disabled)   Claude Fable 5 is currently unavailable. Learn more:
https://www.anthropic.com/news/fable-mythos-access

Selecting it or running `/model Fable` returns:
Model 'Fable' is not currently available for your account. Claude Fable 5 is currently unavailable.

Steps to Reproduce

  1. claude (Max plan, v2.1.198)
  2. /model → observe "5. Fable (disabled)"
  3. /model Fable, /model fable → "not currently available for your account"
  4. Exit, run claude --model claude-fable-5 → session runs on Fable 5 successfully

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.198

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

  • Screenshot attached: two sessions side-by-side, same version/account — left shows the disabled picker entry, right shows a working Fable 5 session started via --model.
  • Possibly related: model availability flags cached during the June 12–30 export-control suspension not being re-fetched/invalidated after re-enable.

Session ID: 7a2001fe-945b-4ee9-ac58-4b0a403f323c
Session ID: 3c0bee64-32d9-4a8b-bf1b-c2c0f4dba4a4

<img width="1918" height="1029" alt="Image" src="https://github.com/user-attachments/assets/915bfc72-d60f-42a3-89a5-c61fcac88954" />

View original on GitHub ↗

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