Unclear It is not clear whether this fixes a real problem with sparse worktrees or only reorganizes how the options are built.
What
A worktree is a second working copy of a git repository, in its own folder, that Claude Code can create so work happens apart from your main checkout. How worktrees are placed and created changed:
- Where a worktree is allowed to live is now worked out from an anchor instead of a fixed path from the repository root. The 'Cannot create worktree:' error messages are unchanged.
- Naming, clash detection, repairing leftover worktrees and removal now check several candidate folders, including the anchor's resolved path, instead of one. A leftover is reported as one "whose .git file points to another location".
- When creating a worktree, the
--no-trackand branch arguments now go into the same argument list as the rest of thegit worktree addcommand, which also gets--no-checkoutwhenworktree.sparsePathsis set. Before, they were added to a different list.
Why
Worktrees may be found and placed differently when the repository's path can be reached in more than one way, and sparse worktrees (ones that check out only some paths) should now receive their branch arguments.
Names in the bundleworktree.sparsePaths
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear whether this fixes a real problem with sparse worktrees or only reorganizes how the options are built.