/model: picker checkmark tracks the default instead of the active session override; full model ID silently drops the [1m] suffix

Status Open
Reported on v2.1.222
Maintainer reply None cached
Activity 2 comments · opened Aug 14, 2026

Environment

  • VS Code extension anthropic.claude-code 2.1.222 (darwin-arm64), macOS 26.5.2
  • Session model: claude-fable-5 (set via /model in an earlier session / carried by the session)

Bug 1: model-picker checkmark shows the saved default, not the effective model

With the session actively running Fable 5 (confirmed by /model with no args: Current model: Fable 5), opening the model picker shows the checkmark on "Default (recommended) — Opus 5 with 1M context". The Fable row carries no indicator.

The status line and the picker disagree about the same session: the text says Fable, the checked row says Opus. I spent a day believing review runs were on Opus when they were on Fable.

Expected: the checkmark (or a second indicator) reflects the model actually serving the session, or the picker distinguishes "your default for new sessions" from "what this session is running."

Bug 2: [1m] suffix silently dropped when combined with a full model ID

/model opus[1m]            → Set model to claude-opus-5[1m]     ✅ suffix honored
/model claude-fable-5[1m]  → Set model to claude-fable-5        ❌ suffix silently dropped

The short-name form honors the 1M-context suffix; the full-model-ID form accepts the input but applies less than was asked, with no warning. If the combination is unsupported, an error would be better than a silent partial apply.

(Report drafted with Claude Code from the affected session.)

View original on GitHub ↗

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