{"version":"2.1.275","anchor":"new-bash-risk-explanation-for-env-p","canonical_anchor":"new-bash-risk-explanation-for-env-p","heading":"New bash risk explanation for env -P","tier":"notice","area":"Bash Tool","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/new-bash-risk-explanation-for-env-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### New bash risk explanation for `env -P`\n\nClaude Code now explains the risk of running env -P with a relative directory\n\n**What**\n\nClaude Code's bash command safety analyzer, which explains why a command might be risky before it runs, now has a specific explanation for `env -P`: when given a relative directory, the program `env` runs is looked up starting from the directory you launched the command in, not from a fixed location. This joins existing explanations for commands that wrap other commands or run without a fixed shell, like `parallel`, `script`, `su`, and `sudo`.\n\n**Why**\n\nThis helps you understand why `env -P` with a relative path is flagged, since it means the actual program executed depends on where you happen to be standing when you run the command.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}