Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] In VSCode extension, is model switching via /model isolated per chat session? Seems like it might not be. [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#53246•Fetched 2026-04-26 05:20:39
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
JohnUrbanJohnUrban
Participants
github-actions[bot]github-actions[bot]JohnUrbanJohnUrban
Timeline (top)
labeled ×5commented ×1unlabeled ×1

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

What's Wrong?

This impacts multi-agent workflows where different models are used for different roles (e.g., Opus for audit, Sonnet for implementation).

This issue is really a question or questions about current behavior. Its bug status depends on the answer(s).

  • Using VSCode Claude Code extension
  • Two chat windows open simultaneously
  • Window A set to Opus
  • Window B changed to Sonnet via /model
  • /model in Window A still reports Opus
  • But behavior suggests it may actually be using Sonnet (possible mismatch), and it reports itself as Sonnet instead of Opus

Concern:

  • Model selection might be shared/global rather than per-session
    • Does selecting a new model in chat B also change it silently for chat A?
  • what is shown by /model in a chat window may be stale or misleading if it is changed in another chat window
    • if the /model changes silently in chat A, it definitely is not reflected when looking at the GUI to see what model and Effort are selected

What Should Happen?

Expected:

  • Model selection should be clearly scoped (per chat vs global)
  • Selecting a model in one chat should never affect the model being used in another
  • /model should reflect actual execution model, not cached state

Impact:

  • Difficult to trust model behavior during multi-window workflows

I understand that this may not be a bug. So please interpret it as a clarifying question that was motivated by thinking it might be acting like this, which would certainly be something to fix.

Thank you for your time and patience, and the great tool

Error Messages/Logs

Steps to Reproduce

  • Open VSCode
  • Open VSCode Claude Code extension chat
  • Window A: Select Opus with Extra High Effort (or any model with any effort)
  • Window A: Do some work with it
  • Window B: Open a new chat to work in parallel
  • Window B: Select a different model and effort; for example, Sonnet with High Effort.
  • Window B: Do some work with it
  • Go back to Window A to prompt some more work
  • Did the model in Window A change? (for example to Sonnet with High Effort)?
  • If so, the model and effort reported are incorrect.

Performance changes in Window A after the model change in Window B made me concerned about this. I apologize if the concern is not justified.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.112 (Claude Code)

Platform

Other

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

I am not using Terminal actually. Just the VSCode extension.

extent analysis

TL;DR

The issue might be resolved by ensuring that model selection is scoped per chat session, rather than globally, to prevent unexpected model changes in multi-window workflows.

Guidance

  • Verify if the model selection is indeed global by checking the behavior of other chat windows after changing the model in one window.
  • Check the documentation or source code of the Claude Code extension to see if there are any settings or configurations that can be used to scope model selection per chat session.
  • Test the behavior of the /model command in different chat windows to see if it reflects the actual execution model or a cached state.
  • Consider filing a feature request to improve the clarity of model selection and scope in the Claude Code extension.

Example

No code snippet is provided as the issue is related to the behavior of the Claude Code extension and not a specific code implementation.

Notes

The issue may not be a bug, but rather a clarifying question about the behavior of the Claude Code extension. The solution may involve changing the configuration or settings of the extension, or filing a feature request to improve its behavior.

Recommendation

Apply workaround: Until the issue is resolved, users can try to use separate VSCode instances or workspaces to isolate the model selection and prevent unexpected changes.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#orchestration issue#cache issue#memory leak#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] In VSCode extension, is model switching via /model isolated per chat session? Seems like it might not be. [1 comments, 2 participants]