Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.302 ·

Worktree resume can skip reusing an existing worktree when no saved state is found

When resuming into a worktree with no recorded state, Claude Code may now prepare it again rather than reuse it as is

Under the hood Internal Changes
JSON All of v2.1.302
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.

See this entry in the whole of v2.1.302 →

Feedback