{"version":"2.1.309","anchor":"headless-sandboxed-git-wrap-returns-null-when-sandbox-does-n","canonical_anchor":"headless-sandboxed-git-wrap-returns-null-when-sandbox-does-n","heading":"Git commands are no longer counted as sandboxed when the sandbox did nothing","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/headless-sandboxed-git-wrap-returns-null-when-sandbox-does-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Git commands are no longer counted as sandboxed when the sandbox did nothing\n\nWhen running headless, Claude Code no longer reports a git command as sandboxed if the sandbox left the command unchanged\n\n**Unclear.** What Claude Code then does with a git command that could not be sandboxed is not stated.\n\n**What**\n\nThe sandbox limits what a command can touch on your computer. When Claude Code runs headless (without its interactive screen), it can wrap git commands in the sandbox. If the sandbox hands back the command unchanged, meaning it did not actually wrap it, Claude Code no longer reports the command as sandboxed. Before, it always did.\n\n**Why**\n\nA sandbox that silently does nothing is no longer treated as protection that is in place.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}