Repository navigation
[BUG] Cancel (✕) doesn't terminate the running command — window stays blocked until manual kill #245
Description
Summary
Pressing the cancel (✕) button on a running command does not terminate the underlying process. The command keeps running and the window stays blocked until the process is killed manually or the extension is fully restarted. Raised in the community Discord and confirmed by a maintainer.
Steps to reproduce
- Start a task that runs a long-running / blocking terminal command.
- Press the ✕ (cancel) button while it is still running.
- Observe the behavior.
Expected
✕ cancels the task and terminates the spawned process, unblocking the window immediately.
Actual
The process is not killed; it must be terminated manually (or the extension fully restarted) before the window is usable again.
Notes
- Related to but distinct from [BUG] Tasks logs occasionally disappear completely when pressing the "Stop" button during AI response. #208 (that issue is about task logs disappearing when pressing Stop; this one is about the process itself not being terminated).
- Happy to help with a fix and/or regression test coverage.
Environment
- Zoo Code (reported on 3.54.1; likely not version-specific)
- VS Code / VS Code Insiders
Activity
proyectoauraorg commentedon May 22, 2026
Claiming.
I filed this one and I'm set up to take it. The cancel (✕) path doesn't terminate the underlying process, so the terminal stays blocked until a manual kill.
Plan:
@edelauna I'll follow up on Discord for assignment, per CONTRIBUTING. 🙌
edelauna commentedon May 23, 2026
As discussed, my preference would be to leverage vscode and try to walk towards leveraging the Task API and CustomExecution.
fix(terminal): terminate running process when task is cancelled (Zoo-…
fix(terminal): retry Ctrl+C for processes needing multiple SIGINT (Zo…
fix(terminal): retry Ctrl+C for processes needing multiple SIGINT (Zo…