{"version":"2.1.290","anchor":"worktree-registration-check-distinguishes-not-pointing-back","canonical_anchor":"worktree-registration-check-distinguishes-not-pointing-back","heading":"Broken Git worktree links are detected more directly","tier":"notice","area":"Worktrees","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/worktree-registration-check-distinguishes-not-pointing-back","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Broken Git worktree links are detected more directly\n\nWhen a Git worktree's link does not point back to its repository, Claude Code now treats it as unregistered without guessing from the error text\n\n**Unclear.** What a user sees differently after this change is not shown.\n\n**What**\n\nA Git worktree is an extra working folder linked to the same repository. When checking a worktree fails, Claude Code now records a reason. If the reason is that the worktree does not point back to its repository, Claude Code treats it as unregistered straight away.\n\nBefore, Claude Code decided this by matching the error text. It now only does that when no reason was recorded.\n\n**Why**\n\nThis changes how Claude Code recovers worktrees whose links are broken.\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}