opencode (default mode) closes entire terminal window on Linux / i3wm #24077

Description

Summary

Running the opencode command in its default mode (which starts both the server and the TUI in the same process) causes the entire terminal window to close — not just the opencode process exiting, but the emulator window itself disappearing. Running opencode serve and opencode attach <url> as two separate processes works perfectly, which strongly suggests the bug is in the combined server+TUI startup path.

Environment

• opencode version: 1.14.21
• OS: Ubuntu (Linux)
• Window manager: i3wm
• Shell: zsh with oh-my-zsh
• Terminal emulators tested (all reproduce the bug): xterm, Terminator, GNOME Terminal
• Installation path: ~/.opencode/bin/opencode
• Installation method: curl installer (curl -fsSL https://opencode.ai/install | bash) — inferred from binary location at ~/.opencode/bin/opencode

Steps to reproduce

1. Open any terminal emulator (xterm, Terminator, GNOME Terminal — all reproduce).
2. Run opencode (default mode, no subcommand).
3. The TUI briefly appears, then the entire terminal window closes.

Expected behavior

The TUI should start and remain running until the user exits it. The terminal emulator window itself should never be closed by opencode.

Actual behavior

The terminal emulator window disappears entirely. The shell process and the emulator process both terminate. On the next session, running opencode reproduces the same crash.

What works (workaround)

Splitting the server and TUI into two separate processes works reliably:

# Terminal 1
opencode serve --port 4096
# prints: http://127.0.0.1:4096
 
# Terminal 2
opencode attach http://127.0.0.1:4096

In this mode, the TUI runs normally and the terminal does not close. This strongly suggests the bug is in the code path that launches server + TUI in a single process.

Diagnostic work already done

I ran an extensive elimination pass. The following were all tested and ruled out as causes:

Strace findings

Running strace -f -o /tmp/opencode-strace.log opencode and grepping for fatal signals showed no SIGSEGV, SIGABRT, SIGKILL, SIGTERM, or SIGHUP delivered to the main opencode process. Child processes exit cleanly with exit_group(0) (one exited with exit_group(1), a grep subprocess whose command resolution I couldn't reconstruct from the log alone). The process disappears without any visible crash signature.

The strace does show child processes resetting job-control signal handlers (SIGTSTP, SIGTTIN, SIGTTOU set to SIG_DFL) and redirecting stdin via dup2(3, 0) — consistent with opencode spawning shell subprocesses for tool calls during startup.

My guess at the mechanism (not confirmed): the process that starts both server and TUI may be reparenting or detaching in a way that causes the controlling-TTY session leader to die, which then propagates up to the emulator. But this is speculation — someone familiar with the opentui integration would be far better placed to diagnose the real cause.

Additional notes

• "Reinstalling" appeared to fix it temporarily in earlier sessions. After full diagnosis, this was likely coincidental timing rather than a real fix — the crash reproduces consistently from a clean state.
• The attach-based workaround is stable and usable indefinitely, so this is not blocking me personally, but the default opencode command being unusable on a common Linux configuration (Ubuntu + i3wm) seems worth fixing.

Plugins

linear (disabled)

OpenCode version

1.14.21

Steps to reproduce

I installed in the morning, and at night or in the next day the problem occurs when I open the opencode. The last times I just reinstalled, but this time I was able to build this workaround.

Screenshot and/or share link

No response

Operating System

Ubuntu 24.04.4 LTS

Terminal

xterm, Terminator, GNOME Terminal