Repository navigation
Warp mode + interactive Q&A: all input captured (mouse clicks, Enter, Ctrl+C) — user must force-close terminal #27302
Description
Description
When using warp mode (/warp) in a worktree session and the agent triggers the interactive Q&A mode (e.g., via the question tool during planning/decision-making), all user input is completely captured — no action can be taken:
- Mouse clicks on confirm/cancel buttons do nothing
- Enter key does nothing
- Ctrl+C (or Cmd+C) does not exit — normally this would abort the interactive Q&A
- The only way to recover is to force-close the terminal window (Ghostty + Fish)
When the session is forcibly terminated, OpenCode reports "interactive Q&A aborted by user" on next launch, confirming the question was never dismissed.
Root Cause Hypothesis
The warp flow (/warp) manipulates a dialog stack via dialog.clear(), dialog.replace(), etc. It appears the warp dialog lifecycle leaves a modal overlay or event capture layer that intercepts all input — both mouse and keyboard — and never releases it. The entire TUI event loop for the session becomes blocked.
Key code locations:
packages/opencode/src/cli/cmd/tui/routes/session/question.tsx— QuestionPrompt withonMouseUpand key bindingspackages/opencode/src/cli/cmd/tui/component/dialog-workspace-create.tsx— warp dialog lifecyclepackages/opencode/src/cli/cmd/tui/ui/— dialog/overlay components
The fact that even Ctrl+C is captured suggests the issue is at the TUI event loop or dialog overlay level, not just the QuestionPrompt component.
Severity
High — user is completely locked out of the session and must force-kill the terminal, potentially losing unsaved work/context.
Steps to Reproduce
- Start OpenCode in a worktree with warp mode enabled (
/warp) - Issue a command that causes the agent to use the
questiontool (interactive Q&A) - The question prompt appears
- Try clicking buttons, pressing Enter, pressing Ctrl+C — none work
- Must force-close the terminal window (e.g., Ghostty + Fish) to recover
Workaround
None in-session. Only recovery is force-closing the terminal.
Environment
- OpenCode version: latest (dev branch)
- Mode: warp (
/warp) - Platform: macOS
- Terminal: Ghostty + Fish
Related Code
packages/opencode/src/cli/cmd/tui/routes/session/question.tsxpackages/opencode/src/cli/cmd/tui/component/dialog-workspace-create.tsxpackages/opencode/src/cli/cmd/tui/ui/(dialog overlay components)
Activity
[-]Warp mode + interactive Q&A: confirm button does nothing, cannot cancel, stuck in question prompt[/-][+]Warp mode + interactive Q&A: confirm/cancel buttons do not respond (mouse clicks swallowed)[/+][-]Warp mode + interactive Q&A: confirm/cancel buttons do not respond (mouse clicks swallowed)[/-][+]Warp mode + interactive Q&A: all input captured (mouse clicks, Enter, Ctrl+C) — user must force-close terminal[/+]transportrefer commentedon May 13, 2026
Update after reproducing this outside
/warp:This no longer looks specific to
/warp, Ghostty/fish, or Secure Keyboard Entry. I found a narrower reproduction around the interactive Q&A custom-answer state:questionprompt.Type your own answer/Other).Confirmtab.option 1, and submit that edit, Confirm starts working again.Looking at
packages/opencode/src/cli/cmd/tui/routes/session/question.tsx, this appears to be stalestore.editingstate:selectTab(index)changestabandselected, but does not clearediting.enabled: dialog.stack.length === 0 && !store.editing.store.editing && !confirm().store.editing === trueandconfirm() === true, neither the edit Return binding nor the Confirm Return binding is active.That also explains why clicking/navigating between steps still works while Confirm itself does not. A likely fix is to clear
editingwhen leaving a question tab, or ensure the Confirm tab can submit/escape even if a stale custom-answer editor state is true.luksch commentedon May 20, 2026
same here on cachyos with the opencode plugin in vs code.
dreamorosi commentedon Jun 13, 2026
I'm facing the same issue and it's blocking
/warpusage - @kommander any chance you could look into this and see if the linked PR solves it?rekram1-node commentedon Jun 23, 2026
Automated: closing question issues.
GitHub Issues are for bug reports and feature requests only — questions / support are no longer tracked here.
If this is a bug or feature request, please open a new issue with the appropriate template.
rekram1-node commentedon Jun 23, 2026
Reopening – this was incorrectly closed by automated question-issue cleanup. Sorry for the noise.
github-actions commentedon Aug 23, 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.