{"version":"2.1.323","anchor":"bash-command-safety-parsing-tweaks","canonical_anchor":"bash-command-safety-parsing-tweaks","heading":"Bash safety check reads variable-style arguments with a new rule","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/bash-command-safety-parsing-tweaks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Bash safety check reads variable-style arguments with a new rule\n\nThe Bash safety check now uses a new pattern to spot arguments that look like variable assignments or array entries\n\n**Unclear.** Which commands, if any, are now approved or refused automatically differently from before.\n\n**What**\n\nWhen Claude wants to run a shell command, Claude Code checks the command to decide whether it is safe to run without asking you. Part of that check looks for arguments that set a variable, such as `NAME=value` or `NAME+=value`.\n\nThat test now uses a new rule. The rule also matches array forms such as `NAME[1]=value`, and assignments in general.\n\n**Why**\n\nThe set of read-only commands that Claude Code approves automatically may change slightly in unusual cases.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}