[BUG] selected model not clear, the statusline does not show updated model

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/18270
2. https://github.com/anthropics/claude-code/issues/15467
3. https://github.com/anthropics/claude-code/issues/15226

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

Confirming this bug on macOS.

Reproduction confirmed:

• Session A: /model sonnet → Status bar correctly shows 'Sonnet 4.5'
• Session B (separate terminal): /model opus → Both sessions' status bars now incorrectly show 'Opus 4.5'
• Verified with /model command: Session A is still actually using Sonnet (correct behavior)
• Only the status bar display is wrong (UI bug, not functional bug)

Root cause:
The statusLine script receives correct per-session data via stdin, but Claude Code appears to use a globally shared rendering cache. When any session updates its status bar, all sessions display that same output.

Impact:

• UX/Trust issue: Users cannot trust the status bar to show the correct model
• Cost concern: Users may think they're accidentally using expensive models (Opus) when they're actually on cheaper ones (Sonnet/Haiku)
• No functional impact: Actual model usage is correct, only display is broken

Environment:

• Platform: macOS (Darwin 25.2.0)
• Claude Code version: 2.0.76+
• Multiple concurrent sessions in separate Terminal.app windows
• Custom statusLine configured in ~/.claude/settings.json

Related issues:
This is the same bug originally reported in #9106 (closed due to inactivity) and duplicated in #15226, #16595, #17820, #18270. The issue has persisted across multiple versions since October 2025.

Seconded - confirmed again as a bug, duplicate under #25885

I see this with both Windows native and macOS Claude Code. It doesn't even require multiple sessions. Just an out-of-band change to ~/.claude/settings.json.

1. Start Claude code
2. Use /model opus
3. Observe statusline's data.model.display_name shows Opus 4.6
4. Edit ~/.claude/setting and change with "model": "sonnet"
5. Issue !ls to update the statusline
6. Observe statusline now shows Sonnet 4.5

Still hitting this on Linux (Arch, Claude Code v2.1.44, Opus 4.6).

The root cause is clear: the statusline payload's model.id / model.display_name is read from shared state (~/.claude/settings.json or equivalent), not from the session's actual active model. Any /model switch in any window overwrites the shared preference, and every other window's next statusline render picks up the stale value.

Why this matters more than it might seem:

For users running custom statuslines, the model name is the #1 most important signal — it's how you confirm you're actually on the model you think you're on. When it lies, you lose trust in the entire statusline. I've seen this cause real confusion: thinking I'm on Sonnet when I'm actually burning Opus tokens, or vice versa.

Suggested fix: The statusline JSON builder should read the model from the session's in-memory state (whatever was negotiated with the API), not from disk. Each session already knows what model it's using for API calls — that's the value that should be in the payload.

This has 5+ duplicate issues filed over multiple months (#25885, #21121, #20939, #23659, #18270). The stale label should probably come off — the bug is very much alive.

I am also experiencing this issue using multiple Claude instances via Windows Terminal. I did find that changing the model of the instance with the wrong status model to a different model and then back to the model I actually want to use, updates the status appropriately. So there must be some error in the logic for retrieving the current model if the instance is using the default.

Reproducing this on v2.1.59 on macOS. Steps: run /model to switch from Opus 4.6 to Sonnet, the command confirms "Set model to sonnet (claude-sonnet-4-6)" but the status bar still shows "Opus 4.6". Only fix is starting a new session.

Screenshot attached (will upload shortly) — shows the /model output saying Sonnet in the transcript, while the status bar at the bottom still reads Opus 4.6.

<img width="1120" height="1064" alt="Image" src="https://github.com/user-attachments/assets/fe522ee0-936a-4a58-b04b-98736807057a" />

Yeah that's happened to me many times, it's worse if you have multiple terminals open because they're all scrambled

elect a model in one select a model in another One of these will not have t

Steps to reproduce:

1. Open Claude Code session A, change model to Opus 4.6
2. Open a new Claude Code session B (different terminal window)
3. In session B, Claude's system context reports "claude-sonnet-4-6" via self-identification
4. But the status bar at the bottom still shows "Opus 4.6"

Expected: System context and status bar show the same model
Actual: Status bar shows Opus 4.6, Claude self-reports as Sonnet 4.6

Environment: Windows Terminal, MSYS shell, Claude Code CLI

adding another bug to this. as the context size is being missed as well.

on the left I have Opus 1 Million. and the right I have Sonnet 200K. the context side in the status line is showing the context side of the Sonnet Agent now, not the Opus 1M. this fixes itself, once a prompt is made to the agent though.

<img width="2704" height="263" alt="Image" src="https://github.com/user-attachments/assets/68b47ba0-814c-4148-be07-551993047597" />

now it's getting confusing which model i am using, causing compaction on Claude Code because i am thinking i am working with Opus model 1 Million

<img width="636" height="157" alt="Image" src="https://github.com/user-attachments/assets/7bfad1d3-b22e-4010-9020-1126dd294ddf" />

Still happening.

Still reproducible on v2.1.77 (macOS Darwin 25.2.0).

After switching from Sonnet 4.6 → Opus 4.6 via /model, the statusline JSON input continues to report the account's default model:

{
  "model": {
    "id": "claude-sonnet-4-6",
    "display_name": "Sonnet 4.6"
  }
}

Meanwhile, the transcript correctly records "model": "claude-opus-4-6" on every assistant message. So the actual model is correct — it's just the statusline data that's stale.

Setting "model": "opus" in settings.json works as a workaround (avoids needing /model override), but the statusline should reflect the active model regardless of how it was selected.

5+ duplicates have been filed and closed pointing back here — this is still a live issue.

This is a duplicate of #37596, which was fixed as of version 2.1.85.

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.