Model picker selects Opus 4.7 1M when choosing Opus 4.7 (200k), possibly after compaction

Bug

In the Claude Code model picker (Ctrl+I) there are two Opus 4.7 entries:

• Opus 4.7 (default 200k context)
• Opus 4.7 1M

Selecting Opus 4.7 (the 200k variant) appears to set the model to Opus 4.7 1M instead. The picker UI shows the checkmark on the chosen entry, but the active model indicator at the bottom shows the 1M variant.

I want to flag two possible distinct bugs — I cannot fully separate them from the client side:

1. Picker / UI bug: clicking Opus 4.7 (200k) visually resolves to Opus 4.7 1M in the active-model indicator.
2. Routing / billing bug: even if the UI shows 1M, it is unclear whether the actual request is routed to the 1M variant or 200k. Only Anthropic backend logs can confirm this.

The second is the more serious case. I do not have direct evidence from billing/usage that the request was billed as 1M — flagging the UI behavior and asking for a backend check.

Environment

• Claude Code: desktop app (Windows)
• OS: Windows 11 Pro 10.0.26200
• Effort: High
• Account plan: Max

Steps to reproduce (suspected)

1. Open model picker (Ctrl+I).
2. Click Opus 4.7 (the 200k variant, not the 1M one).
3. Observe the active-model indicator at the bottom — it shows Opus 4.7 1M.

Expected

Selecting Opus 4.7 (200k) should keep the model at the 200k variant.

Actual

Selection appears to switch / resolve to the 1M variant.

Compaction hypothesis

I suspect this may only occur in resumed / compacted sessions, not fresh ones. I have not confirmed in a clean session yet — will follow up in a comment.

Evidence

Screenshot of the picker in this session attached separately by user. Will follow up with: (a) which model variant actually responded to the next message, (b) whether the bug reproduces in a clean session without compaction.

Ask

Could the team confirm from backend usage logs whether requests in affected sessions were routed to Opus 4.7 200k or Opus 4.7 1M?