Bug: `opencode run` and TUI exits hang on v0.15+

[jlrosende]

Summary

• On OpenCode 0.15.0 and later, the CLI launched with opencode run <prompt> never returns control to the shell; it finishes streaming output but the process keeps running until interrupted with Ctrl+C.
• In the interactive TUI on the same versions, issuing /exit or pressing Ctrl+C closes the interface visually, yet the terminal prompt never comes back—the process must still be terminated with Ctrl+C.
• Downgrading to 0.14.7 immediately restores the correct behaviour, confirming this is a regression introduced in the 0.15.0 line.

Steps to Reproduce

Scenario A – opencode run

1. Install OpenCode 0.15.0 or later.
2. Run opencode run "say hello" --print-logs inside a project directory.
3. Wait for the response to finish streaming.
4. Observe that the command never exits back to the shell; the cursor sits on a blank line until you press Ctrl+C.

Scenario B – TUI /exit

1. Start the interactive TUI (opencode <path|project>).
2. After the assistant finishes a task, enter /exit or press Ctrl+C to leave the session.
3. The TUI clears and disappears, but the shell prompt does not return; pressing Ctrl+C is still required to regain control.

Expected Behavior

• opencode run should terminate automatically once the assistant finishes processing the prompt.
• /exit or Ctrl+C inside the TUI should gracefully shut down the session and immediately return the shell prompt.

Actual Behavior

• opencode run stays attached to the session indefinitely, leaving the terminal blocked until interrupted.
• The TUI window closes, yet the underlying process continues running and the shell prompt never reappears on its own.

Environment

• OpenCode: 0.15.0, 0.15.1, 0.15.2 (works as expected on 0.14.7)
• Platforms tested:
  • Windows 11 (WSL2 Ubuntu 24.04)
  • Fedora 42 (bare metal)
• Shells/Terminals: Windows Terminal (WSL), GNOME Terminal and Ghostty on Fedora (bash and zsh)

Additional Notes

• Clearing caches, reinstalling, or switching providers/models does not resolve the hang.
• --print-logs does not show any obvious error; logs end after the final session.prompt ... finish-step entry.
• Downgrading to 0.14.7 is the only workaround identified so far.

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• TUI exits but process hangs (no shell return) when opencode.json is present #1717: TUI exits but process hangs (no shell return) when opencode.json is present - Similar hanging behavior on TUI exit, requires Ctrl+C to regain shell prompt
• On exit - hangs in terminal #854: On exit - hangs in terminal - Reports hanging behavior after running requests and exiting
• /exit hangs after new session #1810: /exit hangs after new session - Specifically mentions /exit hanging after new session creation

Feel free to ignore if none of these address your specific case.

[rekram1-node]

Do you have an mcp server? Wonder what could be causing the hang

[jlrosende]

I'm currently using GitHub's MCP (the remote version) for development. I've tried disabling them using the enabled parameter, and the problem persists. I've also commented on the configuration, and the problem persists.

[rekram1-node]

I think I saw a pr that might fix this, ill get back to u on that

[veracioux]

@rekram1-node I couldn't reproduce this without MCP servers. I have also observed no difference between 0.14.7 and latest versions. One thing I did observe is that opencode hangs for a few seconds before exiting if session title generation is pending. I've addressed this in #3083.

@jlrosende Is it possible that you didn't wait long enough before pressing Ctrl+C? Also, it might be that you don't have 100% controlled conditions - you might have project-local config files or something that is configuring MCP servers as enabled. Are you able to reproduce using XDG_CONFIG_DIR=nonexistent opencode run <prompt> in a Linux environment?

[jlrosende]

I've been able to run more tests on the client in newer versions, and I've even managed to create a remote MCP server, which I've caused to experience various network errors. The certificate validation and DNS resolution errors are the errors that caused the process to freeze and not release when closing the TUI or terminating the process in command mode.