OpenCode background service hangs Terminal.app #51329

Activity

1. hugo

   changed the title [-]OpenCode background service hangs Terminal.ap[/-] [+]OpenCode background service hangs Terminal.app[/+] on Sep 25, 2026
2. github-actions

   assigned

   rekram1-node

   on Sep 25, 2026
3. github-actions commented on Sep 25, 2026

   

   github-actionsBot

   on Sep 25, 2026 – with GitHub Actions

   Contributor

   More actions

   ---

   This issue might be related to existing reports about background-service lifecycle and process cleanup. Please check:

   • #50633: the Desktop background opencode-cli service remains running after the app closes; the report requests clean shutdown (Windows).
   • #45938: reports macOS process-cleanup/orphan behavior on exit, though the observed symptom differs.
4. opencodejr commented on Oct 28, 2026

   

   opencodejrBot

   on Oct 28, 2026

   Contributor

   More actions

   Thanks for the detailed report and the video! In v2, opencode starts a shared background service on purpose, and it keeps running after the command ends. What you're seeing is how macOS reacts to that service: Terminal.app can't quit cleanly and macOS reports a leaked background process. That only happens on macOS with Terminal.app, and our automated sandbox runs Linux, so it couldn't reproduce this. A maintainer with a Mac will need to look at it.

   In the meantime, you can try turning off the background service (available since v2.1.4):

   opencode service set disabled true

   Each CLI call then runs its own private server and doesn't leave a service behind. To go back, run opencode service unset disabled. It would help if you could say whether Terminal.app quits cleanly with this setting, and which exact version opencode --version prints.

   Related: #50633, where the Desktop app's background service keeps running after the app closes. A commenter there sees "Running in Background" on macOS 27.