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
Dialogs should keep keyboard focus when a question prompt appears #29999
When a modal dialog is already open and the TUI enters question mode, keypresses that should control the dialog can be handled by the question prompt instead.
For example, if the command palette is open and a question prompt becomes active, keys intended for the command palette can contribute to answering the question rather than navigating or selecting inside the command palette.
Global leader shortcuts can also remain active while a dialog is open. For example, pressing the leader key inside the command palette can still start a global leader sequence, and matching follow-up keys can dispatch app/session commands from inside the dialog.
Expected behavior
When a modal dialog is open, the dialog should own keyboard input.
Question-mode bindings should not handle keys before the active dialog gets a chance to handle them, and app/session global shortcuts should not run from inside an open dialog.
Actual behavior
Question-mode bindings can handle keypresses even though a modal dialog is already open.
Global leader shortcuts can also still be triggered while a dialog is open.
Plugins
No response
OpenCode version
1.15.12
Steps to reproduce
For question prompt:
Start a session where the assistant will ask a question.
Open a dialog, such as the command palette, before the question is asked.
This issue might be a duplicate of existing issues. Please check:
Question Tool Keyboard Conflict and Agent Switch Issue #7496: Question Tool Keyboard Conflict and Agent Switch Issue — describes a similar keyboard event bubbling problem where question-mode keypresses conflict with other TUI components (tab key not consumed by QuestionPrompt, triggering agent switch instead)
For keybind-related issues, please also check our pinned keybinds documentation: #4997
Activity
github-actions commentedon May 30, 2026
This issue might be a duplicate of existing issues. Please check:
For keybind-related issues, please also check our pinned keybinds documentation: #4997
kommander commentedon May 30, 2026
Yes, the dialog keymap layers need higher priority. I'll fix that.
leo0o7 commentedon May 30, 2026
Thanks! I opened PR #30000 for this in case it's useful. Happy to adjust it based on your review.
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.