{"version":"2.1.323","anchor":"sandbox-filesystem-rules-extended","canonical_anchor":"sandbox-filesystem-rules-extended","heading":"Sandbox write rules now include extra rules from the filesystem settings","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/sandbox-filesystem-rules-extended","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Sandbox write rules now include extra rules from the filesystem settings\n\nThe sandbox now builds extra rules from your whole filesystem configuration, in addition to its allowWrite and denyWrite lists\n\n**Unclear.** What the extra rules contain is not stated, so it is unclear which paths are newly restricted.\n\n**What**\n\nThe sandbox is a protected environment that limits what commands run by Claude Code can touch. Before, its file rules came only from the `allowWrite` and `denyWrite` lists, which say where commands may and may not write. Claude Code now also adds a further set of rules drawn from the whole filesystem section of the sandbox configuration.\n\n**Why**\n\nWrite restrictions in the sandbox may now be stricter than the two lists alone would make them.\n\n- Area: Sandbox\n- Names: `allowWrite`, `denyWrite`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}