Model visibility and session sync issues between VS Code and terminal

[zzkevin2019]

1. No model name display in VS Code extension

There is no way to see which model is being used in the VS Code extension. The terminal has /model, /status, /context, and the customizable status line, but none of these are available in VS Code. Users have to guess or trust the VS Code setting, which may not reflect what's actually being used (see issue #3 below).

Request: Display the active model name somewhere in the VS Code UI (e.g., status bar, panel header, or equivalent of the terminal status line).

2. Session state doesn't sync between VS Code and terminal

When resuming a terminal session that is concurrently active in VS Code:

• Messages sent in VS Code do not appear in the terminal's view of the session
• The terminal appears to load a snapshot from when the session was last saved, not the live state

Steps to reproduce:

1. Start a session in VS Code
2. Resume the same session in terminal (claude --resume)
3. Continue the conversation in VS Code
4. Check the terminal - new VS Code messages are missing

Expected: Either real-time sync, or a warning that the session is active elsewhere.

3. Model ambiguity when session spans VS Code and terminal

When a session started in VS Code (configured for Sonnet 4.5) is resumed in the terminal (where /model shows Opus 4.6), it's unclear which model is actually being used. VS Code reports Sonnet 4.5 (based on its settings/system prompt), while the terminal reports Opus 4.6. There's no authoritative way to resolve the conflict from within VS Code.

Additionally, /context initially showed a different model than /status and the status line within the same terminal session, though this resolved after exiting and re-entering the session.

[github-actions]

Found 3 possible duplicate issues:

1. [DOCS] Clarify UX differences between Terminal CLI and VS Code Extension #13528
2. [BUG] VS Code Extension has an incomplete slash command list compared to the CLI version #8590
3. [FEATURE] Support custom status line in VSCode extension (like CLI's statusline-command) #20207

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[zzkevin2019]

Only point #1 (model visibility in VS Code) overlaps with #20207, which requests custom status line support in the VS Code extension. I've upvoted that issue.

However, points #2 and #3 are distinct issues not covered by any of the suggested duplicates:

• I want to use openrouter #2 - Session state doesn't sync between VS Code and terminal: When a session is active in both VS Code and terminal simultaneously, messages sent in one don't appear in the other. This is a session management issue, not a feature parity issue.
• Claude is either blank or non-interactive #3 - Model ambiguity across interfaces: When a session spans both VS Code and terminal, different interfaces report different models (e.g., VS Code says Sonnet 4.5, terminal says Opus 4.6), with no way to determine which is actually being used.

These are separate bugs/concerns that aren't addressed by the linked issues.