{"version":"2.1.314","anchor":"bash-permission-check-treats-uncertain-writes-as-ask","canonical_anchor":"bash-permission-check-treats-uncertain-writes-as-ask","heading":"Bash permission checks handle uncertain writes in combined commands differently","tier":"notice","area":"Bash Tool","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/bash-permission-check-treats-uncertain-writes-as-ask","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Bash permission checks handle uncertain writes in combined commands differently\n\nWhen a combined shell command includes a write Claude Code cannot be sure about, an 'ask' result is no longer cut short early\n\n**Unclear.** Whether this leads to more or fewer permission prompts for commands that start with variable declarations is not clear.\n\n**What**\n\nWhen Claude wants to run a shell command made of several commands joined together, Claude Code checks each part and merges the results to decide whether to run it, block it, or ask you first. Before, if the first result was \"ask\" and not a block, Claude Code returned \"ask\" straight away. Now, when that result comes from a write Claude Code cannot be certain about, it does not stop early and keeps merging the other results.\n\n**Why**\n\nThis affects how commands that start with variable declarations are checked for permission.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}