{"version":"2.1.312","anchor":"bash-timeout-telemetry-records-who-stopped-the-command","canonical_anchor":"bash-timeout-telemetry-records-who-stopped-the-command","heading":"Usage data now records who stopped a shell command","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/bash-timeout-telemetry-records-who-stopped-the-command","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Usage data now records who stopped a shell command\n\nWhen a shell command is stopped or times out, Claude Code's usage data now records who stopped it\n\n**What**\n\nWhen a shell command that Claude runs is stopped or times out, Claude Code sends a usage report about it. That report now says who stopped the command, and draws the reason for the stop from a second source as well as the first.\n\n**Why**\n\nThe usage data can now tell apart a command you stopped, one the system stopped, and one that ran out of time.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}