Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Process ManagementArea: what it touches
Internal ChangesKind: in v2.1.317,
Internal ChangesSection of the release
Unclear Whether SIGTERM is still sent somewhere else before the forced stop is not known.
What
Claude 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.
That 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.
Why
This 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.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether SIGTERM is still sent somewhere else before the forced stop is not known.