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 ·

Leaving an existing worktree now uses a shared check for keep or clean up

Claude Code uses one shared check to decide whether to keep or clean up a worktree, including one you entered that already existed

You'll notice Improvements
JSON All of v2.1.302
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
WorktreesArea: what it touches
ImprovementsKind: in v2.1.302,
ImprovementsSection of the release

Unclear It is not clear what the new check tests or what its cleanup step removes from an existing worktree.

What

A worktree is a separate working copy of a git repository. Claude Code now uses one shared check to decide whether to keep or clean up a worktree. Before, it cleaned up only worktrees it had created itself and that were not managed by a hook. When you leave a worktree that already existed before you entered it, Claude Code now runs a cleanup step for it before finishing.

Why

This can change what is left behind on disk when you leave a worktree that already existed.

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 doubtIt is not clear what the new check tests or what its cleanup step removes from an existing worktree.

See this entry in the whole of v2.1.302 →

Feedback