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 ·

Worktrees can get numbered names, and removal checks more carefully for commits

Claude Code can now give a new worktree a numbered name, and when removing one it checks more carefully for commits

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

Unclear When Claude Code picks a numbered name instead of the requested one is not stated.

What

A worktree is a second working copy of a git project in its own folder, so work can happen there without touching your main copy. Claude Code changes how it handles them:

  • Creating a worktree can now pick a numbered name instead of using the requested name directly. If no usable name is found, it stops with an error saying the name "could not be used for a new worktree".
  • Removing a worktree now looks at what the worktree is pointing at (its own branch, another branch, or no branch) to count its commits, instead of counting only from its latest commit. This deeper check is controlled by a server-side setting.
  • A new option controls keeping worktrees inside a given folder.
Why

This reduces worktree name clashes and the chance of removing a worktree that holds commits you still need.

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 doubtWhen Claude Code picks a numbered name instead of the requested one is not stated.

See this entry in the whole of v2.1.304 →

Feedback