{"version":"2.1.323","anchor":"sandbox-filesystem-policy-resolution-changed-order","canonical_anchor":"sandbox-filesystem-policy-resolution-changed-order","heading":"A relaxed sandbox override can now end up strict","tier":"notice","area":"Sandbox","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/sandbox-filesystem-policy-resolution-changed-order","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### A relaxed sandbox override can now end up strict\n\nThe sandbox file policy is now worked out in a new order, so an override asking for the relaxed policy can be overruled and end up strict\n\n**Unclear.** What the further condition is, and so when a relaxed override is overruled, is not known.\n\n**What**\n\nThe sandbox is the restricted space Claude Code runs commands in. Its file policy can be strict or relaxed. Claude Code now decides which one applies in this order:\n\n- An override set to false: strict.\n\n- A further condition: strict, unless `filesystem.disabled` is true in a config.\n\n- An override set to true: relaxed.\n\n- Otherwise: the configured `filesystemPolicy`, including `relaxedIfForced`.\n\nBefore, any override was used directly. True gave relaxed and false gave strict.\n\n**Why**\n\nAsking for the relaxed policy no longer guarantees it. The sandbox may stay strict.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: yes"}