{"version":"2.1.323","anchor":"worktree-creation-and-resume-refuse-when-git-ref-targets-are","canonical_anchor":"worktree-creation-and-resume-refuse-when-git-ref-targets-are","heading":"Worktrees are refused when git could write outside the repository through a link","tier":"notice","area":"Worktrees","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/worktree-creation-and-resume-refuse-when-git-ref-targets-are","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Worktrees are refused when git could write outside the repository through a link\n\nClaude Code now refuses to create a worktree, and keeps the old base on resume, when the git folder holds links or hard-linked entries\n\n**What**\n\nA worktree is a separate working folder of a git repository. Claude Code now checks the repository's git folder before making one. If git could write outside the repository through any of these, Claude Code refuses to create the worktree:\n\n- a link to somewhere else\n\n- a symbolic ref, which is a git pointer to another name\n\n- a hard-linked entry, a file shared with another location\n\nWhen resuming a worktree in that state, Claude Code keeps the old base instead of updating it. The error message tells you to use a plain clone. The check sits behind a server-side switch that is on unless it is switched off remotely.\n\n**Why**\n\nWorktrees made with git-new-workdir or by copying a repository with hard links stop working. Cloning the repository normally fixes it.\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}