{"version":"2.1.317","anchor":"bash-tool-start-telemetry-can-be-skipped-per-session","canonical_anchor":"bash-tool-start-telemetry-can-be-skipped-per-session","heading":"Shell commands may no longer record a start event in every session","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/bash-tool-start-telemetry-can-be-skipped-per-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Shell commands may no longer record a start event in every session\n\nClaude Code now records a start event for a shell command only when a per-session check passes, and otherwise skips it\n\n**What**\n\nWhen Claude Code runs a shell command through its Bash tool (the tool it uses to run terminal commands for you), it records a start event for usage reporting. It used to record that event for every command. It now records it only when a check tied to the current session passes, and skips it otherwise.\n\nWhen the start event is recorded, it now also notes whether the command ran inside an agent worktree. A worktree is a separate working copy of a git repository.\n\n**Why**\n\nSome sessions will no longer send this start event for each shell command. Running the commands themselves is not affected.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}