{"version":"2.1.287","anchor":"shell-snapshot-telemetry-gains-duration-and-capture-method-f","canonical_anchor":"shell-snapshot-telemetry-gains-duration-and-capture-method-f","heading":"Shell snapshot timing is now measured, and Bash commands get an extra PATH step","tier":"internal","area":"Bash Tool","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/shell-snapshot-telemetry-gains-duration-and-capture-method-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Shell snapshot timing is now measured, and Bash commands get an extra PATH step\n\nClaude Code now records how long its shell snapshot takes and how it was captured, and adds an extra PATH step before Bash commands\n\n**Unclear.** What the extra PATH addition puts on the path is not stated.\n\n**What**\n\nWhen Claude Code takes a snapshot of your shell setup, it sends usage data about whether the snapshot worked. That data now also records two things:\n\n- how long the snapshot took, in milliseconds\n\n- which capture method was used\n\nBefore, the report carried no details at all.\n\nSeparately, the setup Claude Code places in front of each Bash command now adds something to `PATH`, the list of folders your shell searches for programs. This step runs before the line that sets `BUN_OPTIONS`.\n\n**Why**\n\nThe snapshot runs when a session starts, so this lets the time it adds to start-up be measured.\n\n- Area: Bash Tool\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}