Description
If you have two (or more) sessions/conversations going, each one running their own model (for different tasks), changing the model selection in one will inadvertently change the selection for other sessions as well. This can cause accidental switching (such as to more expensive models) without the user realizing.
For example, I start SESSION 1 with Claude Opus and have it start processing. Then I open a new SESSION 2, and choose ChatGPT 5.4, and have that one start processing. Returning back to SESSION 1 and responding will now inadvertently also use SESSION 2's model selection instead of maintaining session-specific selectors that they already show until I start responding.
Plugins
None
OpenCode version
v1.2.27
Steps to reproduce
- Start SESSION 1 with Claude Opus and have it start processing.
- Then open a new SESSION 2, and choose ChatGPT 5.4, and have that one start processing.
- Return back to SESSION 1 and responding will now inadvertently also use SESSION 2's model selection instead of maintaining session-specific selectors that they already show until I start responding.
Screenshot and/or share link
No response
Operating System
Windows 11 Pro
Terminal
No response
Description
If you have two (or more) sessions/conversations going, each one running their own model (for different tasks), changing the model selection in one will inadvertently change the selection for other sessions as well. This can cause accidental switching (such as to more expensive models) without the user realizing.
For example, I start SESSION 1 with Claude Opus and have it start processing. Then I open a new SESSION 2, and choose ChatGPT 5.4, and have that one start processing. Returning back to SESSION 1 and responding will now inadvertently also use SESSION 2's model selection instead of maintaining session-specific selectors that they already show until I start responding.
Plugins
None
OpenCode version
v1.2.27
Steps to reproduce
Screenshot and/or share link
No response
Operating System
Windows 11 Pro
Terminal
No response