{"version":"2.1.309","anchor":"worktree-git-guard-handling-of-variable-assignments-before","canonical_anchor":"worktree-git-guard-handling-of-variable-assignments-before","heading":"Worktree isolation checks variables set before git commands differently","tier":"notice","area":"Worktrees","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/worktree-git-guard-handling-of-variable-assignments-before","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Worktree isolation checks variables set before git commands differently\n\nThe worktree guard now treats variable assignments placed before a git command differently, which appears to tighten what it allows\n\n**Unclear.** Exactly which commands are now refused is not clear.\n\n**What**\n\nWorktree isolation keeps Claude working in its own separate copy of a git repository. A guard checks git commands so they cannot reach outside that copy. A command can begin with variable assignments, such as `GIT_DIR=...` placed before the command name, which change how the command runs.\n\nThe guard now finds the last such assignment before the command and checks earlier assignments differently from it, with extra conditions. Before, each assignment was checked the same way.\n\n**Why**\n\nThis is a change to a safety guard, and it appears to tighten the check against assignments that could redirect git.\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}