You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
sdk: server.close() does not terminate underlying opencode process when run via wrappers (e.g., Deno) #21628
Currently, calling server.close() in the SDK only terminates the immediate process wrapper (like deno) but leaves the actual opencode binary running as an orphaned process. This results in the network port remaining occupied and requiring manual cleanup (e.g., fuser -k).
If your issue is specifically about the SDK's server.close() not propagating a termination signal to the spawned opencode binary (rather than the web command or desktop wrapper), it may be worth keeping open as a distinct SDK-specific tracking issue. Otherwise, consider commenting on one of the above.
Activity
github-actions commentedon Apr 9, 2026
This issue might be a duplicate of existing issues. Please check:
ctrl+con the web command; yours coversserver.close()via the SDK with Deno wrappers.opencode-clisidecar process not terminated when the parent (Electron) is closed, leaving orphaned processes.If your issue is specifically about the SDK's
server.close()not propagating a termination signal to the spawned opencode binary (rather than the web command or desktop wrapper), it may be worth keeping open as a distinct SDK-specific tracking issue. Otherwise, consider commenting on one of the above.rekram1-node commentedon Apr 10, 2026
Yeah i think ik the cause, it's the node wrapper isnt forwarding signals to the child correctly. Ez to fix.
rekram1-node commentedon Apr 10, 2026
just need to update bin/opencode.
Looking to see if we can kill the node wrapper tho.
github-actions commentedon Jul 3, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.