{"version":"2.1.314","anchor":"env-prefix-detection-in-shell-command-parsing-no-longer-requ","canonical_anchor":"env-prefix-detection-in-shell-command-parsing-no-longer-requ","heading":"Commands that start with a path-like variable value are now read differently","tier":"notice","area":"Bash Tool","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/env-prefix-detection-in-shell-command-parsing-no-longer-requ","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Commands that start with a path-like variable value are now read differently\n\nClaude Code now also detects variable assignments at the start of a shell command when the value begins with `\/`, `~` or `$`\n\n**Unclear.** It is not clear what the new check tests, so the effect on permission prompts is unknown.\n\n**What**\n\nA shell command can start by setting a variable, as in `FOO=\/x cmd`. Claude Code reads these settings when it looks at the commands it runs. It used to ignore any setting whose value began with `\/`, `~` or `$`. Now it detects those as well, and a separate check decides how each one is handled.\n\n**Why**\n\nThis is likely to change how Claude Code judges commands like `FOO=\/x cmd` when it decides whether a command is safe or needs your 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"}