Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
WorktreesArea: what it touches
Internal ChangesKind: in v2.1.302,
Internal ChangesSection of the release
Unclear The extra condition that must hold alongside a missing record is not known, so it is unclear when a worktree will no longer be reused.
What
A worktree is an extra working copy of a git repository. When Claude Code sets one up, it looks for a recorded state for it, meaning a saved commit. That lookup now reports either a recorded commit or that nothing was recorded. When nothing was recorded and a further condition holds, Claude Code no longer takes the path that reuses the existing worktree. Only the saved commit, rather than the whole record, is now passed on to the setup step.
Why
This changes when an existing worktree is reused and when it is prepared again.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe extra condition that must hold alongside a missing record is not known, so it is unclear when a worktree will no longer be reused.