{"version":"2.1.323","anchor":"sandbox-git-protection-handles-glab-config-folder-and-worktr","canonical_anchor":"sandbox-git-protection-handles-glab-config-folder-and-worktr","heading":"Sandbox now protects glab's settings folder and handles worktrees","tier":"notice","area":"Sandbox","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/sandbox-git-protection-handles-glab-config-folder-and-worktr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Sandbox now protects glab's settings folder and handles worktrees\n\nThe sandbox now write-protects glab's per-repository settings folder and handles git worktrees and enclosing .git folders\n\n**What**\n\nThe sandbox, the restricted space that limits what Claude Code's commands can touch, protects more git-related locations:\n\n- glab's per-repository settings folder is now write-protected, with new warnings. glab is GitLab's command-line tool.\n\n- A repository's own worktrees are now taken into account. A worktree is an extra checkout of the same repository in another folder.\n\n- A .git folder in a folder further up is now handled. When the sandbox cannot examine it, it records that.\n\n- Some block rules are now skipped.\n\n**Why**\n\nThe sandbox now covers more places where a command could change git or glab behavior.\n\n- Flag `tengu_mighty_thimble`: Not enough to say (read for one account on one subscription tier against v2.1.323; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}