Repository navigation
TUI stops responding to user input after first prompt #8229
Description
Description
The TUI is not responding for me. I can reproduce the error consistently on Pop OS 22.04 LTS desktop. The cursor continues to blink but when typing there are no characters accepted. The frozen input persists indefinitely (as far as I can tell). I tried reinstalling the binary with recent updates (to no avail).
As a test I tried spamming letters after submitting the prompt. I can see that the app continues to respond for several seconds/ms after the prompt is sent. The TUI freezes shortly after (seemingly when the response is ready from the LLM).
The bug appears to occur on several/all terminal emulators on this machine.
I cannot reproduce this externally on a different Ubuntu server.
Plugins
No response
OpenCode version
1.1.16
Steps to reproduce
Steps to reproduce (stdin from terminal):
opencode
what is 2+2?
the cursor now blinks but typing does nothing
Screenshot and/or share link
normal case:
when spamming letters after clicking Enter:
focusing the opencode app and typing more does not change the text in the text box
Operating System
Pop OS LTS 22.04
Terminal
Terminal, Kitty
Activity
github-actions commentedon Jan 13, 2026
This issue might be related to #8224: "Enter key doesn't submit prompt when @ autocomplete has no matches", which also involves TUI input handling issues after initial interactions.
However, your specific symptom (input freezing on Pop OS after the first prompt response while the cursor blinks) appears unique. A few things to check:
--log-level debug)?This may be environment or terminal emulator-specific.
Ajetski commentedon Jan 13, 2026
I explicitly stated in the problem that it is not related to a particular terminal emulator. Yes this is reproducible across several terminal emulators (modern and traditional TTY). I tried terminal (default), kitty, and terminator (apt package).
It seems to stop responding to stdin as soon as LLM is done streaming repsponse.
I'll try debug mode and report back
Ajetski commentedon Jan 13, 2026
using
--log-leveldoes not appear to report the error or any other info yet.stderris empty. the app works as expected from CLI interface. only TUI integration is broken from what i can tell (usingopencode run --format json "...")kommander commentedon Jan 13, 2026
What if you just run
opencode, no cmd and no arguments?Ajetski commentedon Jan 13, 2026
Yes @kommander. That is how my reproduction is stated. run
opencodewith no flags. write a single prompt.the input box no longer works. ctrl+c or ctrl+d doesn't work. nothing from stdin seems to be processed after a response is sent from the first prompt.
(on this particular machine. i'll stand up another pop os box w/ RDP after work to test a sterile environment)
Ajetski commentedon Jan 13, 2026
I cannot reproduce on another Pop OS machine. Feel free to close for now (although I am still being affected on one machine.) I'll continue to update versions and debug. Thanks
Flip-Liquid commentedon Mar 2, 2026
Having the same issue here. OSX + running opencode 1.2.15 in iTerm2 with tmux. debug logs provide no information that hones in on the issue. although it seems like the issue could be scoped to individual sessions. attaching to a session with
opencode -s <sesh id>will still work even if creating new sessions exhibits the issue OP mentions.@Ajetski have you been able to find a workaround?
github-actions commentedon May 2, 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.