{"version":"2.1.312","anchor":"shell-task-kills-now-record-who-or-what-caused-them","canonical_anchor":"shell-task-kills-now-record-who-or-what-caused-them","heading":"Stopping a background shell command now records what stopped it","tier":"internal","area":"Background Shells","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/shell-task-kills-now-record-who-or-what-caused-them","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Stopping a background shell command now records what stopped it\n\nWhen Claude Code stops a background shell command, it now records whether the session ending, a caller, or the client stopped it\n\n**What**\n\nClaude Code can run shell commands in the background while it keeps working. When one of these background commands is stopped, Claude Code now records the cause:\n\n- `session_exit` when the command is stopped because the session ended.\n\n- The name of whatever asked for the stop, in other cases.\n\n- `client` when no caller is named.\n\n**Why**\n\nThis is diagnostic information about why background commands stopped. It does not change anything you need to do.\n\n- Area: Background Shells\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}