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
I Can't press enter when use opencode in TUI #23219
Since today my opencode 1.4.11 and use it in Terminal when i finish give message. and press enter to execute code. It doesn't execute the message.
I Shall open last session message and open new message. and the enter function is work.
I think its new bug.
Oh I use it in windows 11 terminal
If your issue is different from these, please add more details (opencode version, steps to reproduce, terminal used) to the dedicated template fields to help distinguish it.
I'm on 1.17.18 and I've hit the same bug. I can answer all the AI questions, but at the end, enter does not work, and there is not an option to submit with the cursor, so I'm stuck.
I am on 1.18.14 and I hit the same bug today. I answered the AI questions in plan mode, and at the end, the Enter key is not working. Not able to submit with the cursor either.
Can we reopen this? I'm hitting the same thing, and so are others. There are also some other related issues mentioned above that look like duplicates. My guess is that the descriptions aren't cleaned up to describe the behavior clearly enough, and people create new issues instead. It would help to have a canonical issue for something that affects a critical path in the tool.
EDIT: It looks like #16610 is the canonical issue.
We still have this issue 1.18.33, enter wont submit in plan mode or build mode, alt+enter does works (new line), but enter to submit wont do anything. Any solution?
We still have this issue 1.18.33, enter wont submit in plan mode or build mode, alt+enter does works (new line), but enter to submit wont do anything. Any solution?
most likely fs.inotify.max_user_instances are exhausted. Just bump it up in sysctl.conf and vibe will probably start doing its thing again
Activity
github-actions commentedon Apr 18, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is different from these, please add more details (opencode version, steps to reproduce, terminal used) to the dedicated template fields to help distinguish it.
lammabing commentedon Apr 18, 2026
Simply cannot press Enter or submit, so opencode is unusable now for me. Happened after most recent update.
arienug20 commentedon Apr 20, 2026
After update to new version of 1.4.18 the error is gone. Thank you
faev999 commentedon Jun 24, 2026
I am on 1.17.9 and have the same problem, also slash commands don't work. I am on Linux Mint 22.3 Using the installation via curl.
airampg commentedon Jul 10, 2026
I'm on 1.17.18 and I've hit the same bug. I can answer all the AI questions, but at the end, enter does not work, and there is not an option to submit with the cursor, so I'm stuck.
PS-NaMaN commentedon Aug 7, 2026
I am on 1.18.14 and I hit the same bug today. I answered the AI questions in plan mode, and at the end, the Enter key is not working. Not able to submit with the cursor either.
oatovar commentedon Aug 19, 2026
Can we reopen this? I'm hitting the same thing, and so are others. There are also some other related issues mentioned above that look like duplicates. My guess is that the descriptions aren't cleaned up to describe the behavior clearly enough, and people create new issues instead. It would help to have a canonical issue for something that affects a critical path in the tool.
EDIT: It looks like #16610 is the canonical issue.
mszulfiqar commentedon Aug 26, 2026
cannot press enter in plan mode
neverendingstory commentedon Sep 1, 2026
It happened again
tendermonster commentedon Sep 24, 2026
yup still here haha 1.18.32
danielqba commentedon Sep 30, 2026
We still have this issue 1.18.33, enter wont submit in plan mode or build mode, alt+enter does works (new line), but enter to submit wont do anything. Any solution?
tendermonster commentedon Sep 30, 2026
most likely fs.inotify.max_user_instances are exhausted. Just bump it up in sysctl.conf and vibe will probably start doing its thing again