[FEATURE] Show active model and thinking mode indicators in the VS Code extension panel
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
When working in the VS Code extension (graphical panel mode), there is no persistent way to see which model is active or whether extended thinking is enabled. During long coding sessions it is very easy to forget what configuration you are currently using without actively opening the command menu (/).
This leads to real workflow problems: you might be debugging a complex issue thinking you are on Opus when you are actually on Haiku, or you might assume thinking is enabled when it is not, resulting in lower quality responses without understanding why.
The CLI already provides status line support showing this kind of information, but the graphical VS Code panel has no equivalent. This creates an inconsistency between the two interfaces and makes the VS Code experience less transparent.
Proposed Solution
Add small, always-visible status indicators directly inside the Claude Code panel bottom bar, next to existing elements like "Ask before edit". For example:
Ask before edit | 🧠 Opus 4.6 | 💭 Thinking: ON
These indicators would show at a glance the active model name (Opus 4.6, Sonnet 4.5, Haiku 4.5, etc.) and whether extended thinking is currently enabled or disabled. They should update in real time when the user switches model or toggles thinking via the command menu.
The bottom bar already contains interactive UI elements, so this addition would be consistent with the existing panel design and would not require major layout changes.
Alternative Solutions
Another option would be to display this information in the panel header area or as a small persistent banner at the top of the conversation. However the bottom bar seems the most natural location since it already serves as a status/control area.
Priority
High - Significant impact on productivity
Feature Category
Interactive mode (TUI)
Use Case Example
A developer is working on a complex refactoring task across multiple files. They started the session on Opus 4.6 with thinking enabled. After a break, they come back and continue working, but at some point the model was switched to Sonnet (due to rate limits or an accidental change). Without any visible indicator, they spend 20 minutes wondering why the responses feel less thorough. A simple glance at the bottom bar showing "Sonnet 4.5 | Thinking: OFF" would have immediately clarified the situation.
Additional Context
This was previously requested in #21265 which was closed without the feature being implemented. Issue #26022 also addresses model visibility in VS Code but does not propose a specific UI location. Issue #9488 and #13158 requested thinking mode exposure in the CLI status line, confirming there is broad community interest in this kind of visibility across both interfaces.
Showing cached comments. Read the full discussion on GitHub ↗
15 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Sounds like a valid use case to me!
Seconding this; it would also help to reduce token usage and improve productivity when you forget to switch from to Haiku for straightforward iteration after using Opus for a complex task (especially in new sessions).
+1 to this. I think it's too easy to forget which model you're in, which could waste a lot of $
+1. This would also mitigate a real bug: in resumed sessions the /models picker shows the wrong model as checked (see #65373), so today there is no reliable always-visible indicator of the effective model in the extension. You only find out by running /context manually.
+1 this seems like a really easy thing to implement
and having it as a setting option, means it can be opt in and not fall into being UI bloat for people who dont want it
+1. One addition: please surface the effort level (low/medium/high/max), not just thinking on/off. With Opus 4.8 the reasoning effort is a graded setting changed via
/effort, and that's exactly what's invisible in the panel today. #45873 (closed as a duplicate of this) asked specifically forOpus · max effortnear the prompt input — worth folding that in so the indicator shows the level, not just a binary.+1. This is so necessary. Does anyone have a workaround?
This limitation is becoming increasingly annoying and wasting my token usage, wasting money.
Honestly, how much time would it take a dev of this extension to add this feature? A couple of hours? It just needs to;
Essentially, just do the same as what the Claude desktop app does (also claude.ai site).
<img width="371" height="517" alt="Image" src="https://github.com/user-attachments/assets/19d370e4-1552-449f-962e-c999556715b2" />
In the meantime, Claude built me a usage meter for the macOS menu bar.
Is there an upvote button hidden somewhere? This feature seems ridiculously simple to add a model selector that shows the current model. Please add this needed feature.
I agree with you; it’s incredibly easy to develop, so it seems absurd to me that they haven’t done it yet.
<img width="520" height="346" alt="Image" src="https://github.com/user-attachments/assets/8e5cf103-4159-4e75-bba0-d2db168ca1d7" />
https://github.com/user-attachments/assets/f6c3586f-c93b-4dea-965c-29fdc98389e7
Lmk where to leave my resume.
Thank you @ianwieds it works like a charm !
I have packaged your fix into a repo so it can be maintained and issues can be reported and fixed :
https://github.com/TsKyrk/cc-vscode-statusbar
The code is unmodified, full credit given to Ian in the README. No license defined (MIT I guess?).
Ask Claude Code to install it, or run node claude-code-model-badge.js.
Hello @ianwieds,
I'd like to propose an improvement that adds the 5-hour and 7-day usage windows to the status bar:
<img width="695" height="96" alt="Image" src="https://github.com/user-attachments/assets/e66b94a6-b7ff-4083-a746-40111990f35a" />
The feature is working. Along the way I also hit — and fixed — a rate-limiting issue that shows up when several VS Code windows are open at once.
Would you be willing to release your original script under the MIT license? I'd like to open the project up to contributions so everyone can benefit.