{"version":"2.1.312","anchor":"shell-kill-can-carry-a-stop-label-kill-time-cpu-time-is-sta","canonical_anchor":"shell-kill-can-carry-a-stop-label-kill-time-cpu-time-is-sta","heading":"Stopped shell commands can now say why they were stopped","tier":"internal","area":"Background Shells","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/shell-kill-can-carry-a-stop-label-kill-time-cpu-time-is-sta","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Stopped shell commands can now say why they were stopped\n\nA stopped shell command can now carry a label saying why it was stopped, and its run time is counted up to the moment it was stopped\n\n**What**\n\nWhen Claude Code stops a running shell command (a command run in the terminal on your behalf), it can now attach a label to it. If the command was stopped, its result carries that label so the rest of Claude Code can tell why it ended.\n\nThe time recorded for a stopped command is also measured differently. It now runs up to the moment the command was stopped, not up to the later moment its exit was handled.\n\n**Why**\n\nClaude Code can now tell why a shell command was stopped, and the time it reports for a stopped command is closer to how long the command actually ran.\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"}