{"version":"2.1.317","anchor":"runner-shutdown-abort-no-longer-sends-sigterm-to-the-process","canonical_anchor":"runner-shutdown-abort-no-longer-sends-sigterm-to-the-process","heading":"Shutdown no longer sends SIGTERM directly to programs Claude Code started","tier":"internal","area":"Process Management","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/runner-shutdown-abort-no-longer-sends-sigterm-to-the-process","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Shutdown no longer sends SIGTERM directly to programs Claude Code started\n\nWhen shutdown stops a program Claude Code started, that step no longer sends SIGTERM to it and its children; it schedules a forced stop instead\n\n**Unclear.** Whether SIGTERM is still sent somewhere else before the forced stop is not known.\n\n**What**\n\nClaude Code has a part that starts and watches other programs. When Claude Code shuts down while one of them is running, this step used to send SIGTERM, a signal asking the program and every program it started to stop cleanly, and logged that it was doing so.\n\nThat signal is gone from this step. Claude Code now writes a different log line and schedules SIGKILL, a signal that ends a program at once, to follow after a delay.\n\n**Why**\n\nThis changes how programs started by Claude Code are stopped when it shuts down, which matters for anything that needs to tidy up before it exits.\n\n- Area: Process Management\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}