{"version":"2.1.323","anchor":"git-worktree-guard-rejects-git-helper-names-containing","canonical_anchor":"git-worktree-guard-rejects-git-helper-names-containing","heading":"Worktree sessions refuse git commands that look like git's internal helpers","tier":"notice","area":"Worktrees","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/git-worktree-guard-rejects-git-helper-names-containing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Worktree sessions refuse git commands that look like git's internal helpers\n\nIn worktree-restricted sessions, git commands whose subcommand contains `--` are now refused, because some of git's helpers write outside the worktree\n\n**What**\n\nA worktree is a separate working copy of a git repository. When a session is limited to one, Claude Code checks git commands before they run. That check now refuses a command whose subcommand contains `--` in its name. Names like that belong to git's internal helper programs, and some of those helpers write files outside the worktree.\n\nThe refusal message suggests what to do instead:\n\n- Run the ordinary git command rather than the helper.\n\n- Add the missing space if `--` was meant to start an option.\n\n- Write a file path as `.\/name` so it is not read as a command.\n\nThe message for words that cannot be checked before a command runs was also reworded. It now says such a word may expand when the command runs, or is an option the check does not know.\n\n**Why**\n\nSome git commands that were accepted before in worktree-restricted sessions are now refused. The new message explains how to rewrite them.\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}