{"version":"2.1.281","anchor":"pwd-and-oldpwd-now-count-as-risky-variables-in-the-bash-env","canonical_anchor":"pwd-and-oldpwd-now-count-as-risky-variables-in-the-bash-env","heading":"PWD and OLDPWD now count as risky variables in the Bash env-var check","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/pwd-and-oldpwd-now-count-as-risky-variables-in-the-bash-env","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### PWD and OLDPWD now count as risky variables in the Bash env-var check\n\n`PWD` and `OLDPWD` now always count as risky variables when the Bash check decides whether `rm` or `cd` can take the quick path\n\n**Unclear.** The finding does not say what the quick path skips, such as whether it means running without asking.\n\n**What**\n\n`PWD` holds the shell's current folder and `OLDPWD` holds the previous one. When Claude Code decides whether an `rm` or `cd` command can take its quick path, any reference to these two now always counts as risky and rules the quick path out.\n\nThe same check now also looks at:\n\n- the command's arguments\n\n- files named after `<` (input redirection, which feeds a file into a command)\n\n**Why**\n\nIn practice, more commands that mention these variables, or that use them in arguments or redirects, are kept off the quick path."}