Provide a way to stop all running scripts when OpenCode is interrupted #3057

Activity

1. github-actions commented on Oct 9, 2025

   

   github-actionsbot

   on Oct 9, 2025 – with GitHub Actions

   Contributor

   More actions

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

   • Provide means to disable Ctrl-C #2999: Similar request for Ctrl-C handling - discusses problems with Ctrl-C behavior and the need to disable or modify its functionality
   • bug: /compact is not interruptable #2928: Related to interruption issues - specifically mentions that /compact operations cannot be interrupted, indicating similar process control problems
   • opencode does not exit on ^D #3025: Related exit/termination behavior - addresses the need for proper process termination with ^D, showing similar concerns about process lifecycle management

   Feel free to ignore if none of these address your specific case.
2. rekram1-node commented on Oct 9, 2025

   

   rekram1-node

   on Oct 9, 2025

   Collaborator

   More actions

   ah nice catch we should definitely fix thx

   ❤️React with ❤️3Reacted by William Bruntrager, Kauã Sacramento and PVL
3. rekram1-node

   self-assigned this

   on Oct 9, 2025
4. anntnzrb commented on Dec 21, 2025

   

   anntnzrb

   on Dec 21, 2025

   Contributor

   More actions

   LSP processes have the same problem

   The shell cleanup in shell/shell.ts already has proper SIGKILL escalation:

   process.kill(-pid, "SIGTERM")
   await Bun.sleep(200)
   if (!opts?.exited?.()) {
     process.kill(-pid, "SIGKILL")
   }

   However, LSP processes in lsp/client.ts lack this:

   async shutdown() {
     connection.end()
     connection.dispose()
     input.server.process.kill()  // Just SIGTERM, no escalation
   }

   Missing from LSP cleanup:

   1. No SIGKILL escalation — If the process ignores SIGTERM, it lives forever
   2. No process group kill — Uses process.kill() not process.kill(-pid), so child processes (e.g., tsserver spawned by typescript-language-server) survive
   3. No exit verification — Doesn't confirm the process actually terminated

   Reproduction

   When using git worktrees with parallel operations, each worktree spawns its own LSP set. After the session ends, orphaned tsserver processes remain:

   $ ps aux | grep tsserver
   annt  57149  0.1  0.5  ...  tsserver.js ...
   annt  57195  0.1  0.5  ...  tsserver.js ...
   annt  57275  0.0  0.5  ...  tsserver.js ...
   # ... 7+ processes from different worktrees
   

   Suggested fix

   Apply the same cleanup pattern from shell/shell.ts to lsp/client.ts:

   async shutdown() {
     connection.end()
     connection.dispose()
     const proc = input.server.process
     const pid = proc.pid
     try {
       process.kill(-pid, "SIGTERM")
       await Bun.sleep(200)
       // Check if still running, then SIGKILL
       process.kill(-pid, "SIGKILL")
     } catch {
       proc.kill("SIGKILL")
     }
   }

   Related: #5525 (same root cause, Windows-specific report)
5. anntnzrb commented on Dec 21, 2025

   

   anntnzrb

   on Dec 21, 2025

   Contributor

   More actions

   Opened PRs to address part of this issue:

   • fix(lsp): use Shell.killTree for proper process cleanup #5875 - Fix LSP process cleanup (uses Shell.killTree() + detached: true)
   • fix(pty): use proper process tree cleanup on disposal #5876 - Fix PTY process cleanup (adds killPtyTree() helper)

   These ensure child processes are properly killed when LSP/PTY sessions are disposed. The bash tool abort race condition (where void kill() is fire-and-forget) is a separate issue that will need a follow-up PR.
6. gkp1 commented on Jan 31, 2026

   

   gkp1

   on Jan 31, 2026

   Last edited by gkp1

   More actions

   I am having to manually kill processes that opencode 'forgets' running forever, and they remain consuming my cpu for no reason processing something that I don't know what might be, even if I have used+closed opencode hours ago. I suspect it's those times that opencode runs a task in a sub agent (not sure what its called) and it hangs, and then I close opencode and that's probably what leaves those processes there without being killed.

   Today I used tools @general @explore and chrome web devtools mcp, not sure if any are related. Also not sure if it's the main opencode process or sub processes that remain running in background. Probably sub processes that opencode spawns. I always close opencode by closing the terminal or ctrl c then close terminal. On mint ubuntu 24

   (on screenshot below I had 3 opencode processes (killed 1) running, but I didn't have any opencode terminal open, closed hours ago)

   
7. github-actions commented on Apr 1, 2026

   

   github-actionsbot

   on Apr 1, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
8. github-actions

   closed this as completedon Apr 1, 2026