{"version":"2.1.311","anchor":"shell-parsing-regexes-for-env-var-assignments-and-command-wo","canonical_anchor":"shell-parsing-regexes-for-env-var-assignments-and-command-wo","heading":"Better parsing of variable assignments at the start of shell commands","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/shell-parsing-regexes-for-env-var-assignments-and-command-wo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Better parsing of variable assignments at the start of shell commands\n\nClaude Code can now pick out leading VAR=value assignments and the command words that follow them in shell commands\n\n**Unclear.** Whether this changes which Bash commands are allowed or denied is not stated.\n\n**What**\n\nA shell command can begin by setting variables, for example `FOO=bar make`. Claude Code can now recognise these leading assignments and separate them from the command words that follow. This works with:\n\n- Plain values.\n\n- Array subscripts, such as `ARR[1]=x`.\n\n- Quoted values.\n\n- Values produced by running a command with `$()`.\n\n**Why**\n\nHow Claude Code reads the start of a command can affect whether a command Claude wants to run is allowed automatically, needs your permission, or is denied.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}