Status bar shows wrong model after /compact (shows Opus when session is Sonnet)
Resolved 💬 4 comments Opened Apr 8, 2026 by lamyliu Closed May 21, 2026
Bug Description
After running /compact, the status bar in the header displays the wrong model — showing Opus 4.6 — even though the active session model is Sonnet 4.6.
Steps to Reproduce
- Start a Claude Code session (default model: Opus 4.6)
- Run
/model sonnetto switch to Sonnet 4.6 - Run
/compactto compact the conversation - Observe the status bar after compaction
Expected Behavior
Status bar should show Sonnet 4.6 (the model set via /model before compaction).
Actual Behavior
Status bar shows Opus 4.6 after compaction completes.
However, running /model in the prompt correctly shows currently Sonnet 4.6, confirming the active model is correct.
Screenshots / Evidence
- Header after compact:
Opus 4.6 (1M context) with medium effort · Claude Max /modelcommand output:Set the AI model for Claude Code (currently Sonnet 4.6)
Additional Context
- Claude Code version: v2.1.85
- Subscription: Claude Max
- The discrepancy suggests
/compactmay internally use Opus 4.6 to generate the summary (regardless of the current session model), and the status bar reflects the model used for compaction rather than the current session model. - This is confusing and may also explain unexpectedly high token consumption for Max users, since the compact operation itself may run on Opus even when the user has switched to Sonnet to conserve quota.
Possible Issues
/compactuses Opus internally even when session model is Sonnet- Status bar doesn't update to reflect current session model after compaction
- Or both of the above
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗