{"version":"2.1.295","anchor":"bash-tool-input-command-description-is-accepted-as-descript","canonical_anchor":"bash-tool-input-command-description-is-accepted-as-descript","heading":"Bash tool accepts command_description in place of description","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/bash-tool-input-command-description-is-accepted-as-descript","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Bash tool accepts command_description in place of description\n\nIf Claude sends command_description instead of description to the Bash tool, Claude Code now treats it as the description\n\n**What**\n\nBefore running a request from Claude to use the Bash tool (the tool that runs shell commands), Claude Code tidies up the request's fields. It now handles a field called `command_description`:\n\n- No `description` given: `command_description` is used as the `description`.\n\n- `description` already given: `command_description` is dropped, and Claude Code notes that it did so.\n\nIt also changes how `timeout_ms` is handled. Before, it was always removed. Now it is only removed once it has been turned into `timeout`.\n\n**Why**\n\nRequests where Claude used a slightly wrong field name are accepted instead of being rejected, so fewer command attempts fail.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}