{"version":"2.1.311","anchor":"sandbox-nested-git-config-lock-deny-and-symlink-grant-profi","canonical_anchor":"sandbox-nested-git-config-lock-deny-and-symlink-grant-profi","heading":"Sandbox gains rules for git configuration in nested repositories and for symlinks","tier":"notice","area":"Sandbox","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/sandbox-nested-git-config-lock-deny-and-symlink-grant-profi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Sandbox gains rules for git configuration in nested repositories and for symlinks\n\nThe sandbox's rules now include blocking git configuration lock files in nested repositories and a profile for granting access to symlinks\n\n**What**\n\nThe sandbox is a set of limits on which files and resources commands run by Claude can reach. When Claude Code builds the sandbox's rules, it now adds two things:\n\n- A rule that blocks access to the lock file git uses while it changes the configuration of a repository nested inside another one.\n\n- A profile used to grant access to symlinks, files that point to other files.\n\n**Why**\n\nThis tightens what sandboxed commands can do to git configuration in nested repositories.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}