{"version":"2.1.323","anchor":"bash-tool-timing-telemetry-gains-stall-duration-ms","canonical_anchor":"bash-tool-timing-telemetry-gains-stall-duration-ms","heading":"Bash command timing now records how long a command took to start","tier":"internal","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/bash-tool-timing-telemetry-gains-stall-duration-ms","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Bash command timing now records how long a command took to start\n\nClaude Code now records how long a Bash command took to start, alongside the timing data it already collected\n\n**What**\n\nThe Bash tool is how Claude runs commands in your terminal. Claude Code collects timing data for these commands, and it now records `stall_duration_ms` when it knows how long the command took to start, along with some extra fields. Before, only the total duration and processor time were recorded.\n\nSeparately, the Bash tool's own instructions to Claude changed in the capture taken under this release: the list of files that likely contain secrets and should not be committed now includes `.claude\/settings.local.json`.\n\n**Why**\n\nThe new timing shows how long starting a command takes. The instruction change means Claude should warn you before committing your local Claude Code settings file.\n\n- Area: Telemetry\n- Names: `stall_duration_ms`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}