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
Stuck at permission granting with the Enter key is not working #27875
I'm currently using omo, and the sub agent asks for permission as it cycles invalid tool calls. However, the enter key seems not working. I can use CTRL+Enter to add a new line but I cannot use Enter to confirm. I pressed it for a bunch of times but it just don't work. Now I'm stuck and cannot stop. Both rejecting and approving requires enter to confirm, but I currently failed to confirm. I cannot control opencode now.
If there is any other key to jump out of the approval request, it should be better.
Plugins
oh-my-opencode, opencode-dcp
OpenCode version
latest
Steps to reproduce
I don't know how to reproduce, but I did as follows:
Make a plan
let Atlas execute it parallelly with different agents.
One sub agent uses tools incorrectly for several times, and a loop is detected.
Opencode requires approval, but cannot confirm. It just stucks there.
same, very annoying. when it is stuck you can still hit tab to cycle all the question tabs and change your answers, its just not accepting a key on the final confirm tab
ps, it does not respond to anything, including ctrl+c, I can close opened terminal panes this way but it wont work on opencode stuck on a confirm tab cli push 42 "0x0b" Command sent to pane 42.
Same issue here — Windows 11, Windows Terminal, latest OpenCode.
The specific scenario: when the AI agent asks me a question via the interactive Q&A popup (the question tool), pressing Enter does nothing — the answer never submits. This happens consistently, not just during permission granting. Any dialog that requires Enter to confirm is affected.
Current workaround: Ctrl+C / Esc to dismiss the dialog (or force-close terminal if that doesn't work), then copy both the question and my intended answer, paste everything back into the TUI chat input, and resubmit as a regular message. Clunky, but keeps the session alive.
It seems like the root cause is that these overlay dialogs (permission, question, etc.) don't properly handle the Enter key event on Windows, possibly related to how OpenTUI processes keyboard input (similar to the kpenter vs return issue described in #17457).
Same symptoms — permission dialog options (Allow once, Allow always, Reject) cannot be selected using either keyboard or mouse. Also affects Esc to cancel/stop actions. Not limited to Windows.
Also seeing the same confirm-tab dead zone with the question tool (not just permission prompts) on v1.18.30 (Linux): tab-cycling between question tabs works fine, but the final Confirm tab won't accept any key — Enter, Esc, Ctrl+C all ignored. Only way out is force-closing the terminal.
Activity
github-actions commentedon May 16, 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 16, 2026
Does it work without OmO? If it works with
opencode --purethen it is a plugin issue. Please file an issue with OmO.atjeff commentedon May 18, 2026
This happens with pure. Seems to be the same as #27302
atom8be commentedon May 21, 2026
same, very annoying. when it is stuck you can still hit tab to cycle all the question tabs and change your answers, its just not accepting a key on the final confirm tab
ps, it does not respond to anything, including ctrl+c, I can close opened terminal panes this way but it wont work on opencode stuck on a confirm tab
cli push 42 "0x0b" Command sent to pane 42.Resolved for me in WSL in a version soon after.
skywalker-35 commentedon May 22, 2026
Same issue here — Windows 11, Windows Terminal, latest OpenCode.
The specific scenario: when the AI agent asks me a question via the interactive Q&A popup (the
questiontool), pressing Enter does nothing — the answer never submits. This happens consistently, not just during permission granting. Any dialog that requires Enter to confirm is affected.Current workaround: Ctrl+C / Esc to dismiss the dialog (or force-close terminal if that doesn't work), then copy both the question and my intended answer, paste everything back into the TUI chat input, and resubmit as a regular message. Clunky, but keeps the session alive.
It seems like the root cause is that these overlay dialogs (permission, question, etc.) don't properly handle the Enter key event on Windows, possibly related to how OpenTUI processes keyboard input (similar to the
kpentervsreturnissue described in #17457).lightt77 commentedon Jun 2, 2026
Happening on my macbook+iterm2 too, this is the first time I am seeing this.
ztobs commentedon Jun 5, 2026
Also affected on Linux:
Operating System: Ubuntu 26.04 LTS (Resolute Raccoon)
Kernel: Linux 7.0.0-22-generic x86_64
Desktop: GNOME (Wayland)
Terminal: GNOME Terminal (xterm-256color)
Shell: zsh
Node: v23.1.0
OpenCode version: v1.15.12 through v1.16.0
Same symptoms — permission dialog options (
Allow once,Allow always,Reject) cannot be selected using either keyboard or mouse. Also affectsEscto cancel/stop actions. Not limited to Windows.rquiroga7 commentedon Jul 23, 2026
Also affected by same bug:
Operating System: Ubuntu 22.04.5 LTS (Jammy Jellyfish)
Kernel: Linux 6.8.0-124-generic x86_64
Desktop: GNOME (X11)
Shell: bash
Node: v20.20.2
OpenCode version: v1.18.4 using OpenCode extension in VS Code
lonsun commentedon Aug 20, 2026
Happening to me too. Maddening.
Macbook Pro M5
MacOS 26.5.2 (25F84) (Tahoe)
Ghostty / Fish shell
Opencode TUI 1.18.18
For me neither the Enter key or the Esc key work. So i have to forcefully close the pane to move forward.
If i can help troubleshooting this further then please let me know.
manascb1344 commentedon Sep 26, 2026
Also seeing the same confirm-tab dead zone with the question tool (not just permission prompts) on v1.18.30 (Linux): tab-cycling between question tabs works fine, but the final Confirm tab won't accept any key — Enter, Esc, Ctrl+C all ignored. Only way out is force-closing the terminal.
thdxr commentedon Oct 11, 2026
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (
opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊