{"version":"2.1.317","anchor":"bash-permission-rules-also-match-against-command-text-deny","canonical_anchor":"bash-permission-rules-also-match-against-command-text-deny","heading":"Bash deny and ask rules now also check the full command text","tier":"notice","area":"Permissions","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/bash-permission-rules-also-match-against-command-text-deny","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Bash deny and ask rules now also check the full command text\n\nClaude Code now also checks a shell command's raw text against your deny and ask rules, so a match blocks it or asks you first\n\n**Unclear.** The further condition that decides whether this text check runs is not stated.\n\n**What**\n\nPermission rules are settings that tell Claude Code which actions to block (deny rules) or to confirm with you first (ask rules). The Bash tool is what Claude uses to run shell commands.\n\nBefore, Claude Code split a command line into its separate commands and checked only those pieces against deny rules. It now also searches the raw command text for deny and ask rules:\n\n- A match with a deny rule refuses the command.\n\n- A match with an ask rule shows you a permission prompt.\n\nThis extra check runs only when you have deny or ask rules, and only when a further internal condition is met.\n\n**Why**\n\nRules become harder to get around with unusual quoting or with several commands strung together on one line.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: yes"}