[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.