Repository navigation
Selected model changes for some reason, even the child processes don't take the selected model #12250
Closed as not planned
Description
Description
If switching model, the selected model switches back to big pickle, the child processes are also going back to big pickle even if some other model is selected
Plugins
Oh-my-opencode
OpenCode version
1.1.48
Steps to reproduce
Open opecode
Change the model
Send a message
Voila you're back to the old model
Screenshot and/or share link
No response
Operating System
Macos 26.2
Terminal
No response
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Feb 5, 2026
I've reviewed existing issues and found no exact duplicates for this specific model reversion behavior. However, the following related issues about model handling may be worth checking:
This appears to be a unique issue involving model state not persisting properly when sending messages, especially with child processes. The model switching back to a default ('big pickle') suggests a state management or fallback logic issue specific to how the currently selected model is tracked during message sending.
lee-b commentedon Feb 14, 2026
Seeing this too, since today's v1.2.2 update.
rekram1-node commentedon Feb 14, 2026
@lee-b are u using plugins?
Try without
mblarsen commentedon Feb 17, 2026
Same happens to me using oh-my-opencode-slim
szabolcs-dekany commentedon Feb 25, 2026
Similar thing, started a session in one model, randomly changed to a different one on the fly, seemingly the previously used model
zaxbysauce commentedon Mar 6, 2026
This was not occurring for me but is now happening every message. Windows 11 25H2, OpenCode v1.2.20
bohdansavastieiev commentedon Apr 13, 2026
It seems like the issue is caused by the fact that there are different states for selected models in Build and Plan mode. So if you switch the model in Plan mode, the model selected for Build mode is still the previous one. It feels counterintuitive, especially during workflows where you spend some time in a Plan mode, and then when start to build, the model is different. But I may see the benefit of such decision, so not sure if this is the expected behavior or not.
github-actions commentedon Jul 3, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
lee-b commentedon Jul 3, 2026
I think a large part of the problem is that ctrl-x u effectively undoes any model changes, as well as undoing conversation history. The ux presents ctrl-x u / ctrl-x r as navigating through messages, but it navigates through multiple orthogonal (high?) dimensions of control at the same time: actual history in some senses, but not all senses.