Status bar shows wrong model when running multiple concurrent sessions

Bug Description

When running multiple Claude Code terminal sessions simultaneously with different models (e.g., one session on Sonnet 4.6, another on Opus 4.6), the status bar at the bottom of the terminal can display the wrong model name.

Steps to Reproduce

1. Open a Claude Code session and set the model to Sonnet 4.6
2. Open a second Claude Code session and set the model to Opus 4.6 (1M context)
3. Observe the status bar in the Opus session

Expected Behavior

The status bar should display "Opus 4.6 (1M context)" matching the active model for that session.

Actual Behavior

The status bar displays "Sonnet 4.6" even though:

• /model confirms "Set model to Opus 4.6 (1M context) (default)"
• The thinking indicator shows Opus-specific behavior ("Razzmatazzing... (thinking with high effort)")

Screenshot

The screenshot shows /model output confirming Opus 4.6, Opus-specific thinking indicators, but the status bar reading "Sonnet 4.6":

!status bar showing wrong model

Impact

• Cosmetic only — the actual model routing appears correct (Opus-specific behaviors are present)
• However, it creates confusion about whether the correct model is actually being used, especially for users who rely on the status bar to confirm their model selection

Environment

• Platform: macOS (Darwin 24.6.0)
• Claude Code: CLI terminal
• Multiple concurrent sessions with different model selections