{"version":"2.1.319","anchor":"which-removed-from-the-read-only-bash-command-allowlist","canonical_anchor":"which-removed-from-the-read-only-bash-command-allowlist","heading":"The which command is off the list of commands treated as safe","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/which-removed-from-the-read-only-bash-command-allowlist","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### The `which` command is off the list of commands treated as safe\n\n`which` was removed from the shell commands Claude Code treats as safe, alongside `sleep`, `type`, `expr` and `seq`\n\n**Unclear.** It is not confirmed that this list is what lets a command run without a permission prompt.\n\n**What**\n\nClaude Code keeps a list of shell commands it treats as safe, such as `sleep`, `type`, `expr` and `seq`. `which`, a command that shows where a program is installed, has been taken off that list.\n\n**Why**\n\nA `which` command that used to run without asking may now stop and ask for your permission first.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}