{"version":"2.1.323","anchor":"sandbox-late-symlink-grants-are-vetted-and-write-allows-can","canonical_anchor":"sandbox-late-symlink-grants-are-vetted-and-write-allows-can","heading":"The sandbox checks late shortcut grants and protects GitLab CLI settings","tier":"notice","area":"Sandbox","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/sandbox-late-symlink-grants-are-vetted-and-write-allows-can","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### The sandbox checks late shortcut grants and protects GitLab CLI settings\n\nSandbox setup now checks shortcut-file grants added late, allows writes inside blocked areas where listed, and blocks the GitLab CLI config\n\n**What**\n\nThe sandbox is the restricted environment Claude Code can run commands in, which limits the files they can change. The way Claude Code builds the sandbox's file rules changed:\n\n- Write access granted late through symlinks (shortcut files that point to another location) now goes through a separate checking step. Before, these grants went straight into the rules.\n\n- For each such grant, Claude Code now tries to create the target folder or file and removes matching entries from the blocked list.\n\n- The file rules can now allow writing to particular paths that sit inside an otherwise blocked area.\n\n- Git worktrees (extra working copies of a repository) now have their links guarded.\n\n- The configuration of `glab`, the GitLab command-line tool, is now blocked from writes.\n\n**Why**\n\nThis changes which paths commands inside the sandbox can write to. In particular, they can no longer change your `glab` configuration.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}