{"version":"2.1.299","anchor":"sandbox-macos-write-rules-literaldenywithinallow","canonical_anchor":"sandbox-macos-write-rules-literaldenywithinallow","heading":"The macOS sandbox blocks writes to more specific paths","tier":"notice","area":"Sandbox","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/sandbox-macos-write-rules-literaldenywithinallow","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### The macOS sandbox blocks writes to more specific paths\n\nOn macOS, the sandbox now adds a list of exact paths to block inside otherwise writable folders, plus extra rules derived from existing ones\n\n**Unclear.** It is not stated where the new list of exact blocked paths comes from or whether users can set it.\n\n**What**\n\nThe sandbox limits what commands run by Claude Code can touch. On macOS, its rules for where writing is blocked now include:\n\n- a list of exact paths that are blocked even inside folders where writing is allowed\n\n- extra blocking rules derived from the existing list of blocked paths inside allowed folders\n\nBefore, only that existing list and the built-in list of dangerous paths were used.\n\n**Why**\n\nThe set of places the sandbox refuses to write to is stricter or more precise.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}