{"version":"2.1.323","anchor":"sandbox-excludedcommands-and-deny-lists-now-tightened-by-a-n","canonical_anchor":"sandbox-excludedcommands-and-deny-lists-now-tightened-by-a-n","heading":"Sandbox exclusions can be limited to trusted settings in more situations","tier":"notice","area":"Sandbox","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/sandbox-excludedcommands-and-deny-lists-now-tightened-by-a-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Sandbox exclusions can be limited to trusted settings in more situations\n\nA new condition can now limit `excludedCommands` to trusted settings and make running commands outside the sandbox fail\n\n**Unclear.** It is not clear what the new condition is or when it applies.\n\n**What**\n\nThe sandbox is a fenced-off space where commands run with limited access, and `excludedCommands` lists commands allowed to run outside it. Claude Code already ignored `excludedCommands` from untrusted settings files under one condition. It now does so under an extra condition too. When that condition holds:\n\n- `excludedCommands` is taken only from trusted settings levels.\n\n- Saved deny lists are treated as possibly incomplete.\n\n- The check for running a command outside the sandbox fails.\n\n**Why**\n\nThis can make the sandbox stricter. If commands you listed in `excludedCommands` start running inside the sandbox, this may be the reason.\n\n- Area: Sandbox\n- Names: `excludedCommands`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: yes"}