{"version":"2.1.268","anchor":"bash-tool-telemetry-gains-detailed-shell-command-shape-field","canonical_anchor":"bash-tool-telemetry-gains-detailed-shell-command-shape-field","heading":"Bash tool telemetry gains detailed shell-command shape fields","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/bash-tool-telemetry-gains-detailed-shell-command-shape-field","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Bash tool telemetry gains detailed shell-command shape fields\n\nBash tool telemetry now records a detailed breakdown of each command's shape\n\n**What**\n\nThe telemetry events fired when a bash command succeeds (`tengu_bash_tool_command_executed`) or fails (`tengu_bash_tool_command_failed`) now include a much richer breakdown of the parsed command, on top of the existing `command_type` field:\n\n- the command's class and its first argument (`argv0`)\n\n- the last command's `argv0` in a chain\n\n- whether it used pipes, redirects, chains, subshells, or heredocs\n\n- a count of simple commands within it\n\n**Why**\n\nThis gives more detailed visibility into the structure of bash commands being run, which can help with understanding usage patterns and diagnosing issues, though the underlying `tengu_bash_tool_command_executed` and `tengu_bash_tool_command_failed` gates have no recorded reading yet.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}