[sub-agents] Agents not killed on cancel #23534

Activity

1. tadghh

   added

   bugSomething isn't workingSomething isn't working

   on Apr 20, 2026
2. github-actions

   assigned

   rekram1-node

   on Apr 20, 2026
3. github-actions

   added

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   on Apr 20, 2026
4. github-actions commented on Apr 20, 2026

   

   github-actionsBot

   on Apr 20, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • Background agents cannot be force-interrupted/stopped via ESC #22638: Background agents cannot be force-interrupted/stopped via ESC — similar issue where canceling/stopping sub-agents does not actually terminate them, resulting in continued activity (in that case, ESC doesn't stop the agent; here, the inference API continues being called after cancel)
   • JDTLS (Java Language Server) processes are never terminated after subagent sessions end, causing massive memory leak #15037: JDTLS processes are never terminated after subagent sessions end — related issue about subagent processes not being properly cleaned up after sessions end

   If your issue is specifically about API usage/billing continuing after you cancel a sub-agent (rather than purely the UI not responding to stop), it may be worth noting that distinction to help prioritize the fix.
5. tadghh commented on Apr 21, 2026

   

   tadghh

   on Apr 21, 2026

   Author

   More actions

   YES
6. lrq3000 commented on Apr 26, 2026

   

   lrq3000

   on Apr 26, 2026

   Last edited by lrq3000

   More actions

   OpenCode Server needs to offer a systematic way to kill all agents and subagents on interrupt, otherwise zombie sessions can continue being open in the background or at least the sessions status may not be reflecting the true session state because of zombie sessions that cannot be killed.

   Having a way to force kill a session completely would allow the user to manually reset a session state in case of any error happening, this is extremely important just as task managers are crucial for any OS.

   👍React with 👍1Reacted by Thomas Forrer
7. thdxr

   removed

   bugSomething isn't workingSomething isn't working

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   on May 3, 2026
8. thdxr

   assigned

   nexxeln

   and unassigned

   rekram1-node

   on May 3, 2026
9. github-actions commented on Jul 3, 2026

   

   github-actionsBot

   on Jul 3, 2026 – with GitHub Actions

   Contributor

   More actions

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

    closed this as not plannedon Jul 3, 2026