Repository navigation
Visibly selected Build/Plan mode or Reasoning level is not always what seems to be actually selected #60051
Description
Description
Send a prompt on Max thinking level, but it says it was switched to xHigh (which it was on for the previous prompt). Or send a prompt with Build, but the Agent says it is on Plan and cannot build (it was on Plan in the previous prompt). Then send a prompt AGAIN with Build mode visibly selected, but the Agent still sees Plan mode. Repeat a third time. Then i needed to visibly select Plan mode, and select Build mode again (which was already at least visibly selected) and send another prompt, for the Agent to finally see it was indeed switched to Build mode.
This is in Opencode desktop v2.2.0. It seems that a visible switch is not always registered. Possibly the longer a session takes but not sure if that has a role. It is intermittent, so most of the time it will work correctly. But then suddenly it can think i switched the Reasoning level or the Build/Plan mode back to the previous' prompt selection while i didn't.
Plugins
None enabled currently.
OpenCode version
2.2.0 desktop
Steps to reproduce
Intermittent, but:
- In the middle of a session, switch from Plan to Build mode. Observe it sometimes suddenly still being in Plan mode, with the Agent asking to be put in Build. Only fix is to first select Plan again in the dropdown. Than select Build again (which was already selected, at least visbily, in the first place). Only now does the Agent recognize the switch to Build mode.
- In the middle of a session, switch Reasoning level. For example start on High, later use XHigh for a new prompt and at one point use Max. Notice that for a follow-up prompt, it will suddenly say it was switched to Xhigh. While visibly (just like in the case of the Build mode) Max was selected when you sent the prompt.
Screenshot
No response
Operating System
Windows 11
Terminal
No response
Activity
opencodejr commentedon Oct 28, 2026
Thanks for the detailed report. I wasn't able to reproduce this here: it happens in OpenCode Desktop on Windows, and only some of the time, and the environment I have can only run the terminal UI.
From reading the code, one possible cause (not confirmed) is how the desktop composer decides whether to send an agent or reasoning-level switch with your prompt. It compares your selection with the session state the app has cached locally. If that cache is out of date, it can skip the switch even though the picker shows your new choice. That would explain why selecting Plan and then Build again fixes it. Separately, if Settings → General → follow-up behaviour is set to queue, a prompt sent while the agent is still working keeps the agent and reasoning level the session already has, so check that setting.
A maintainer with the desktop app will need to look into this. Two things would help:
Related issues:
VariableVince commentedon Oct 29, 2026
To answer these questions: