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

New worktrees start from a fixed commit, not a moving HEAD

Claude Code now looks up the exact commit before creating a worktree from HEAD, so the starting point can't shift partway through

You'll notice Bug Fixes
JSON All of v2.1.300
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
WorktreesArea: what it touches
Bug FixesKind: in v2.1.300,
Bug FixesSection of the release
What

A worktree is a second working copy of a git repository in its own folder. HEAD is git's name for the commit you currently have checked out. When Claude Code bases a new worktree on HEAD, it now looks up the exact commit first and creates the worktree from that commit. This covers two cases:

  • The worktree is based on HEAD on purpose
  • Fetching the branch from the remote failed, so Claude Code falls back to your local HEAD

Before, Claude Code passed the name HEAD itself to git.

Why

If HEAD moved while the worktree was being created, the worktree could end up on a different commit than intended. Pinning the commit first stops that. In everyday use you are unlikely to notice a difference.

See this entry in the whole of v2.1.300 →

Feedback