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.304 ·

Removing a worktree now tells apart commits on its current branch and a kept branch

ExitWorktree now separates commits on a worktree's current branch from commits on a kept branch, and can refuse removal until you confirm

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

A worktree is a separate copy of your project checked out in its own folder. ExitWorktree is the tool Claude uses to leave one, and it can remove the worktree as it goes.

When asked to remove a worktree, ExitWorktree now tells apart commits on the branch the worktree is currently on from commits on a branch that is being kept. If the worktree has moved to another branch since it was made, it now says so. It can refuse the removal in more cases, and when it does it tells Claude to confirm with you before trying again with discard_changes: true.

A check for worktrees nested inside the one being removed is also present, but it does not do anything yet in this build.

Why

The more precise checks make it less likely that work is lost by accident when a worktree is removed.

See this entry in the whole of v2.1.304 →

Feedback