{"version":"2.1.277","anchor":"sandboxed-bash-auto-allow-now-excludes-commands-matching-rz","canonical_anchor":"sandboxed-bash-auto-allow-now-excludes-commands-matching-rz","heading":"Sandboxed-bash auto-allow now excludes commands matching rz()","tier":"notice","area":"Bash Safety","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/sandboxed-bash-auto-allow-now-excludes-commands-matching-rz","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Sandboxed-bash auto-allow now excludes commands matching rz()\n\nSandboxed auto-allow for Bash commands now excludes commands matching an additional check\n\n**Unclear.** The finding does not say what kinds of commands the new exclusion check matches.\n\n**What**\n\nWhen sandboxing and \"auto-allow if sandboxed\" are both enabled, Claude Code could previously let a Bash command run without asking for approval. Now that auto-allow also requires that the command does not match a new exclusion check, meaning some commands that would have been auto-allowed before will now still require approval.\n\n**Why**\n\nThis tightens the conditions under which sandboxed Bash commands skip approval, reducing the chance that a command that shouldn't be auto-approved slips through.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}