{"version":"2.1.314","anchor":"bash-read-onlysafety-checker-stricter-handling-of-find-rg","canonical_anchor":"bash-read-onlysafety-checker-stricter-handling-of-find-rg","heading":"Stricter safety checks for find, rg, sort, read, xargs and awk commands","tier":"notice","area":"Bash Tool","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/bash-read-onlysafety-checker-stricter-handling-of-find-rg","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Stricter safety checks for find, rg, sort, read, xargs and awk commands\n\nClaude Code checks more shell commands more strictly before running them without asking, so some will now ask for permission\n\n**What**\n\nBefore Claude Code runs a shell command without asking you, it checks that the command only reads and cannot do harm. Those checks are now stricter for several common commands:\n\n- `find`: refuses option values worked out at run time, and `;` or `+` clause endings stuck onto other text.\n\n- `read` and `getopts`: refuse unquoted wildcard characters such as `*`, `?`, `[` or `{`, which could expand into no word or several words, and values that are risky under the zsh shell.\n\n- `rg`, `sort` and `xargs`: their option values are now checked too.\n\n- `awk`: is also covered by the tightened checks.\n\nNew messages explain when a refusal is because an option's value is worked out at run time.\n\n**Why**\n\nSome commands that used to run straight away will now stop and ask for your permission. That is expected, and it closes ways a command could look harmless but behave differently once the shell expanded it.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}