Repository navigation
TUI stays alive with EOF stdin and no TTY #42234
Description
Reproduction
docker run -d --name opencode-eof node:22-bookworm-slim sleep infinity
docker exec opencode-eof npm install -g [email protected]
timeout -s KILL 8s docker exec opencode-eof opencode </dev/null
docker top opencode-eof -eo pid,ppid,tty,stat,etime,argsActual
opencode does not exit. After the docker exec client is killed, the TUI process remains in the container with no TTY.
Expected
Exit with a clear error when the TUI has EOF stdin and no prompt. Otherwise the process can hold an active exec session indefinitely and prevent auto-sleep for idle environments.
Reacted by Guilherme Salazar
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Aug 13, 2026
This issue might be a duplicate of existing issues. Please check:
opencode runignoring an unused inherited stdin pipe — the core symptom (process hangs when stdin is a non-TTY pipe) overlaps with this report, though [FEATURE]: let opencode run ignore an unused inherited stdin pipe #42064 targets therunsubcommand while this issue targets the TUI mode.xichen1997 commentedon Aug 29, 2026
Hi @kommander, could you take a look into that?
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 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊