{"version":"2.1.310","anchor":"new-growthbook-gated-write-block-on-an-unreadable-gitworkt","canonical_anchor":"new-growthbook-gated-write-block-on-an-unreadable-gitworkt","heading":"Sandbox gains a remotely switched write block for an unlistable .git\/worktrees folder","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/new-growthbook-gated-write-block-on-an-unreadable-gitworkt","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Sandbox gains a remotely switched write block for an unlistable .git\/worktrees folder\n\nThe sandbox can now block writes when a git worktrees folder cannot be listed, controlled by a remote switch that can change without a new release\n\n**Unclear.** Whether this write block is on or off when the server sends no value is not stated.\n\n**What**\n\nThe sandbox is the protective boundary that limits what Claude Code's commands can read and write on your computer. Its settings code now has a rule that blocks writes to a git worktrees folder (`.git\/worktrees`, where git keeps track of extra working copies of a repository) when that folder cannot be listed.\n\n- `unlistableWorktreesDenyApplied` is a new piece of state recording whether this block is in effect. It sits next to the existing state for paired write-deny rules.\n\n- `builtConfigUnlistableWorktreesDenied` is where that state comes from. It is worked out each time a sandbox configuration is built.\n\n- The state is restored when a configuration is installed and compared whenever settings change.\n\n- A change to the matching GrowthBook setting now makes the sandbox reapply its rules. GrowthBook is a service that lets Anthropic turn features on or off remotely.\n\nThe block only covers a worktrees folder that cannot be listed. The release itself does not show whether the switch starts on or off. Nothing has been read about the related gate, `tengu_quiet_medlar`, so its state is unknown.\n\n**Why**\n\nIn practice, the sandbox may now refuse writes inside `.git\/worktrees` when that folder cannot be read. Because the switch is remote, this behaviour can change between sessions even if Claude Code is not updated. If writes to git worktrees are refused inside the sandbox, this rule is one place to look.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}