Skip to content

Blocked TAB switching during predefined answer selection and logical inconsistency in Plan Mode prompts #8867

Closed

Description

@patryksztuczka

Description

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:

  1. Press ESC to dismiss the predefined answers/question mode.
  2. Use TAB to manually switch to Build Mode.
  3. Manually type the command to execute the plan.

Plugins

none

OpenCode version

1.1.20

Steps to reproduce

  1. Enter Plan Mode and describe a task.
  2. 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."
  3. Try to press TAB to switch to Build Mode while these options are visible; the key is blocked.
  4. Select the "Execute" option.
  5. Observe the agent failing or asking for a mode switch, consuming extra tokens in the process.

Screenshot and/or share link

Image Image Image

Operating System

macOS 14.6

Terminal

Ghostty

Activity

  1. github-actions commented on Jan 16, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    Feel free to ignore if none of these address your specific case.

  2. github-actions commented on Mar 26, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions