{"version":"2.1.290","anchor":"bash-tool-telemetry-drops-builtin-capture-wall-clockuptime","canonical_anchor":"bash-tool-telemetry-drops-builtin-capture-wall-clockuptime","heading":"Bash command usage data drops one field","tier":"internal","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/bash-tool-telemetry-drops-builtin-capture-wall-clockuptime","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Bash command usage data drops one field\n\nThe usage data Claude Code records when a Bash command runs or fails no longer includes one field about builtin output capture\n\n**What**\n\nClaude Code records usage data each time its Bash tool (the tool Claude uses to run terminal commands) finishes or fails a command. Those two records, `tengu_bash_tool_command_executed` and `tengu_bash_tool_command_failed`, no longer include the `builtin_capture` field. Separately, the Bash tool's check on file history now receives extra information about the current session.\n\n**Why**\n\nThis only changes what is recorded about commands; running commands works the same way.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}