{"version":"2.1.314","anchor":"bash-static-analysis-tracks-divergent-unset-values","canonical_anchor":"bash-static-analysis-tracks-divergent-unset-values","heading":"Shell command checks handle unset and appended variables differently","tier":"notice","area":"Bash Tool","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/bash-static-analysis-tracks-divergent-unset-values","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Shell command checks handle unset and appended variables differently\n\nClaude Code's checks of shell commands now treat unsetting and appending to variables differently when deciding permissions\n\n**Unclear.** Whether this leads to more or fewer shell commands being allowed without asking is not known.\n\n**What**\n\nBefore running a shell command, Claude Code reads the command to decide whether it can be allowed without asking you. It has changed how it follows variables in that reading, in particular when a command unsets a variable or appends to one. Some commands it now judges too complex to read are marked in a new way.\n\n**Why**\n\nThis can change which multi-part shell commands Claude Code allows on its own and which ones it asks you about.\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"}