{"version":"2.1.317","anchor":"sandbox-adds-macos-write-deny-relaxations-and-relative-write","canonical_anchor":"sandbox-adds-macos-write-deny-relaxations-and-relative-write","heading":"Sandbox gains three new write protections","tier":"notice","area":"Sandbox","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/sandbox-adds-macos-write-deny-relaxations-and-relative-write","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Sandbox gains three new write protections\n\nThe sandbox adds write blocks for relative paths through symlinks, for .git\/remotes and .git\/branches, and a pin on git info folders\n\n**What**\n\nThe sandbox is a fenced-off environment that limits what commands run by Claude Code can write. Its setup now tracks three more protections, each with its own record of whether it was applied:\n\n- Relative-path write-deny twins, which block writes that reach a denied place through a relative path or a symlink (a shortcut to another file or folder). Recorded as `builtConfigRelativeWriteDenyTwins`.\n\n- A legacy remote folders deny, a write block on `.git\/remotes` and `.git\/branches`. Recorded as `builtConfigLegacyRemoteDirsDenied`.\n\n- A pin on git info folders. Recorded as `builtConfigGitInfoDirsPinned`.\n\nOn macOS, the setup also loops over a further set of paths and denies those that fall outside the folders you may write to. The sandbox restarts when the feature flags for any of these three protections change. Before, only `patternWriteDenyTwins` and `unlistableWorktreesDeny` existed.\n\n**Why**\n\nCommands inside the sandbox may now be refused writes they could make before, especially into parts of a `.git` folder or through symlinks.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}