{"version":"2.1.280","anchor":"bash-exit-code-error-classification-now-parses-the-commands","canonical_anchor":"bash-exit-code-error-classification-now-parses-the-commands","heading":"Bash exit-code error classification now parses the command's shell AST for trailing list operators","tier":"internal","area":"Bash Tool","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/bash-exit-code-error-classification-now-parses-the-commands","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Bash exit-code error classification now parses the command's shell AST for trailing list operators\n\nClaude Code now parses a bash command's structure to avoid misreporting exit codes as errors\n\n**What**\n\nWhen Claude Code runs a shell command, it checks the exit code to decide whether the command failed. A new helper now actually parses the structure of the bash command (its abstract syntax tree, a breakdown of how the command is built from pieces like `&&` and `;`) to handle cases where the last part of a command list ends with an operator like `&&`.\n\n**Why**\n\nThis prevents certain commands from being wrongly flagged as failed just because of how they were chained together with `&&` or similar operators, so the error reporting you see for Bash tool calls should be more accurate.\n\n- Area: Bash Tool\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}