{"version":"2.1.257","anchor":"worktree-git-isolation-guard-now-analyzes-complex-shell-tree","canonical_anchor":"worktree-git-isolation-guard-now-analyzes-complex-shell-tree","heading":"Worktree git-isolation guard now analyzes complex shell trees, not just simple commands","tier":"notice","area":"Worktrees","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/worktree-git-isolation-guard-now-analyzes-complex-shell-tree","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Worktree git-isolation guard now analyzes complex shell trees, not just simple commands\n\nThe worktree git guard now parses complex shell commands instead of refusing them all, only refusing what it cannot verify.\n\nThe worktree git-isolation guard, which blocks git commands from escaping an isolated worktree, no longer refuses every non-simple shell command outright. It now parses complex commands (subshells, pipes, etc.) into an AST and only refuses when the command is unparseable, contains an error node, or a regex flags the git invocation as too complex to verify; otherwise it walks the parsed tree looking for actual worktree-escaping redirection.\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}