{"version":"2.1.290","anchor":"bash-command-safety-awkfind-glob-check-extended","canonical_anchor":"bash-command-safety-awkfind-glob-check-extended","heading":"More awk and find commands now ask for permission first","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/bash-command-safety-awkfind-glob-check-extended","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### More `awk` and `find` commands now ask for permission first\n\nClaude Code now asks before running `awk` or `find` commands that trip an extra wildcard check, not only ones with unquoted wildcards\n\n**Unclear.** What the second wildcard check looks for is not clear.\n\n**What**\n\nClaude Code lets some shell commands run without asking you, if it judges them safe. For `awk` and `find`, it already refused to auto-allow commands containing wildcard characters such as `*` that are not in quotes. It now also refuses when a second wildcard check matches. This extra check is on by default.\n\n**Why**\n\nYou will be asked for permission on more `awk` and `find` commands than before.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}