{"version":"2.1.323","anchor":"always-ask-command-rules-now-stop-sandbox-auto-allow","canonical_anchor":"always-ask-command-rules-now-stop-sandbox-auto-allow","heading":"Ask rules now apply to sandboxed commands","tier":"notice","area":"Sandbox","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/always-ask-command-rules-now-stop-sandbox-auto-allow","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Ask rules now apply to sandboxed commands\n\nA sandboxed command that matches one of your ask rules now prompts you instead of being allowed automatically\n\n**What**\n\nClaude Code can run shell commands in a sandbox, a restricted environment that limits what a command can reach. Some sandboxed commands used to be approved automatically. That shortcut applied whenever the sandbox condition held.\n\nNow, if a command matches one of your ask rules, Claude Code skips the automatic approval and asks you first. An ask rule is a permission rule saying Claude Code must always ask before running a command. This check is in two of Claude Code's permission paths.\n\n**Why**\n\nBefore, a sandboxed command could run without the prompt your ask rule was meant to force. An explicit ask rule now wins over the sandbox shortcut.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}