{"version":"2.1.302","anchor":"worktree-entry-tracks-reuse-of-a-worktree-made-elsewhere","canonical_anchor":"worktree-entry-tracks-reuse-of-a-worktree-made-elsewhere","heading":"Claude Code notes when it reuses a worktree made elsewhere","tier":"internal","area":"Worktrees","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/worktree-entry-tracks-reuse-of-a-worktree-made-elsewhere","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Claude Code notes when it reuses a worktree made elsewhere\n\nAfter creating or entering a worktree, Claude Code now checks whether it already existed and was made somewhere else\n\n**Unclear.** What Claude Code does differently when it reuses a worktree made elsewhere is not clear.\n\n**What**\n\nA worktree is a separate working copy of a git repository, so work can happen on one copy without disturbing another. After Claude Code creates or enters a worktree, it now checks whether that worktree already existed and was made somewhere else.\n\n**Why**\n\nClaude Code can now tell apart a worktree it reused from one made elsewhere, which points to different handling of worktrees that already exist.\n\n- Area: Worktrees\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}