{"version":"2.1.286","anchor":"worktree-registration-check-is-more-conservative","canonical_anchor":"worktree-registration-check-is-more-conservative","heading":"Worktree cleanup reports entries it could not check","tier":"notice","area":"Worktrees","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/worktree-registration-check-is-more-conservative","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Worktree cleanup reports entries it could not check\n\nWhen cleaning up a git worktree, Claude Code now reports entries it could not check instead of silently skipping them\n\n**Unclear.** It is not clear where, or whether, this report is shown to the user.\n\n**What**\n\nA git worktree is an extra working copy of a repository, stored in its own folder. Git keeps a record of each worktree it knows about. When Claude Code removes a worktree, it checks whether git still has it registered.\n\nSome records could not be read, for example links or unreadable files. Those used to be skipped without comment. Claude Code now notes them as \"could not be checked\" and reports that git \"may still register this worktree\".\n\n**Why**\n\nCleanup is more cautious. Claude Code no longer assumes a worktree is fully removed when it could not confirm that.\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}