{"version":"2.1.293","anchor":"killing-a-shell-process-skips-escalation-for-an-already-exit","canonical_anchor":"killing-a-shell-process-skips-escalation-for-an-already-exit","heading":"Stopping a shell command no longer escalates if it already exited","tier":"notice","area":"Bash","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/killing-a-shell-process-skips-escalation-for-an-already-exit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Stopping a shell command no longer escalates if it already exited\n\nWhen stopping a shell command, Claude Code now skips the escalation steps if the process has already exited\n\n**What**\n\nWhen Claude Code stops a shell command it started, it first asks the process to stop. Then, as a backup, it forces the process to quit after a delay. It now checks whether the process has already exited before running that backup. It checks again just before the forced stop. If the process is gone, it does nothing more.\n\nBefore, it always went through both steps.\n\n**Why**\n\nThis avoids a forced stop landing on another process that has since taken over the same process ID, the number the system uses to identify a running program.\n\n- Area: Bash\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}