{"version":"2.1.317","anchor":"bash-tool-tail-input-capture-and-telemetry","canonical_anchor":"bash-tool-tail-input-capture-and-telemetry","heading":"The Bash tool can keep a copy of a command's input","tier":"internal","area":"Bash","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/bash-tool-tail-input-capture-and-telemetry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### The Bash tool can keep a copy of a command's input\n\nFor some check-style commands, the Bash tool can now keep a copy of the command's input and add a note about it to the error output\n\n**Unclear.** It is not clear whether the internal switch is on by default, so this may not happen for you.\n\n**What**\n\nThe Bash tool is how Claude runs terminal commands. For commands that look like checks, it can now keep a copy of the command's input and pass it along when the command runs. When it keeps that copy, it adds a note about it to the command's error output.\n\nThis happens only when a few conditions hold:\n\n- An internal switch is on.\n\n- The shell running the command is bash.\n\n- Something that reads the results from outside the command is present.\n\nThe usage data recorded when a Bash command finishes or fails now also notes whether a command was a candidate for this, whether its input was copied and kept, and how many bytes were kept.\n\n**Why**\n\nThis changes what the Bash tool keeps from some commands and adds notes to the output of failed ones.\n\n- Area: Bash\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}