[BUG] Status bar shows "Opus 4.6 (default)" instead of actual effort level on startup

Resolved 💬 2 comments Opened Feb 13, 2026 by PossumGS Closed Feb 13, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

When running multiple Claude Code sessions with different effort levels configured, the status bar always
displays "Opus 4.6 (default)" on startup, regardless of the actual effort level setting for that session.

  • Status bar shows "Opus 4.6 (default)" on startup for all opus sessions
  • The session is actually using the correct effort level (just not displayed correctly)
  • Opening settings shows the effort level is set correctly (e.g., "High Effort")
  • Toggling the effort level setting in the UI (even though it already shows the correct value) forces a refresh

and corrects the status bar display

What Should Happen?

The status bar should display the correct effort level (e.g., "Opus 4.6 (High)" or "Opus 4.6 (Medium)") that matches the session's actual configuration when the session starts.

Error Messages/Logs

Steps to Reproduce

  1. Launch multiple Claude Code sessions with different effort levels using these commands:

```bash
claude --model opus --effort high
claude --model opus --effort medium

  1. Observe the status bar on startup - it shows "Opus 4.6 (Default)" for both sessions
  2. Open settings and check the effort level - it's set correctly (e.g., "High Effort" in one, "Medium Effort"

in the other)

  1. Toggle the setting to another value and back - status bar now displays correctly (e.g., "Opus 4.6 (High)")

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.41

Platform

Anthropic API

Operating System

Other Linux

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

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