{"version":"2.1.274","anchor":"bash-input-command-extraction-bug-fix","canonical_anchor":"bash-input-command-extraction-bug-fix","heading":"Bash-input command extraction bug fix","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/bash-input-command-extraction-bug-fix","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Bash-input command extraction bug fix\n\nFixed a bug where extracting a bash command from message text checked the wrong variable\n\n**What**\n\nClaude Code has an internal helper that looks for a fallback bash command embedded in message text (inside `<bash-input>` tags). It was mistakenly checking an outdated variable left over from a previous loop iteration instead of the current one, so it could look at stale text. It now consistently checks the correct, current text.\n\n**Why**\n\nThis fixes a bug that could cause the wrong bash command to be extracted from a message, since the check was looking at leftover data instead of the actual current input.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}