You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Blocked TAB switching during predefined answer selection and logical inconsistency in Plan Mode prompts #8867
In the new experimental Plan Mode, the UI captures the keyboard focus when predefined answers (buttons) are presented to the user. This prevents the use of the TAB key to manually switch from Plan Mode to Build Mode.
Furthermore, there is a logical inconsistency: the agent often generates "Execute Plan" or "Apply Fix" as a predefined answer while still in Plan Mode. Since Plan Mode lacks write permissions, selecting these leads to a failed attempt, unnecessary re-prompts, and wasted tokens.
Questions for the Team:
Should "Execute" actions even be offered as predefined answers in Plan Mode?
Wouldn't it be more consistent if predefined answers in Plan Mode were reserved for clarifying doubts or refining the plan, rather than triggering execution that the current mode doesn't support?
Workaround Currently, the only way to bypass this is to:
Press ESC to dismiss the predefined answers/question mode.
Use TAB to manually switch to Build Mode.
Manually type the command to execute the plan.
Plugins
none
OpenCode version
1.1.20
Steps to reproduce
Enter Plan Mode and describe a task.
Wait for the agent to generate a plan. If you are "lucky" (the agent's generation is non-deterministic), it will offer a predefined answer such as "Execute Plan" or "Yes, apply fix."
Try to press TAB to switch to Build Mode while these options are visible; the key is blocked.
Select the "Execute" option.
Observe the agent failing or asking for a mode switch, consuming extra tokens in the process.
Screenshot and/or share link
Operating System
macOS 14.6
Terminal
Ghostty
Reacted by tienbg-zigexn, Kinan Lakhdar, dynobo and Georg Graf SPG
Activity
github-actions commentedon Jan 16, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
github-actions commentedon Mar 26, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.