Description
When closing the OpenCode Electron window, the opencode-cli sidecar process is not terminated. Re-launching the app spawns a new opencode-cli instance, causing multiple processes.
SIGTERM via Ctrl+C (when running the binary directly) correctly stops both the Electron window and the sidecar — but simply closing the Electron window does not, regardless of how the app was launched. Somehow running the binary directly, have faster startup time.
I can confirm this also happen in Opencode Electron Desktop on MacOS running on Macbook Air M2.
Plugins
I don't have any installed plugins
OpenCode version
1.2.24
Steps to reproduce
- Open the OpenCode Electron Desktop
- Close the Opencode Electron Desktop
- See the process list, in my case i'm using
btop. opencode-cli process still running.
- Open the OpenCode Electron Desktop again. It will spawn another opencode-cli process.
- I have to kill it manually in order to kill the
opencode-cli process
Screenshot and/or share link
Operating System
ArchLinux x86_64
Description
When closing the OpenCode Electron window, the
opencode-clisidecar process is not terminated. Re-launching the app spawns a newopencode-cliinstance, causing multiple processes.SIGTERM via Ctrl+C (when running the binary directly) correctly stops both the Electron window and the sidecar — but simply closing the Electron window does not, regardless of how the app was launched. Somehow running the binary directly, have faster startup time.
I can confirm this also happen in Opencode Electron Desktop on MacOS running on Macbook Air M2.
Plugins
I don't have any installed plugins
OpenCode version
1.2.24
Steps to reproduce
btop.opencode-cliprocess still running.opencode-cliprocessScreenshot and/or share link
Operating System
ArchLinux x86_64