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

Clearer errors when Claude Code can't find where to start a worktree

When creating a git worktree fails to find its starting point, Claude Code now explains why and how to fix it

You'll notice Improvements
JSON All of v2.1.299
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
ImprovementsKind: in v2.1.299,
ImprovementsSection of the release
What

A git worktree is an extra working copy of a repository that Claude Code can create to work in. When Claude Code cannot work out which commit a new worktree should start from, it now shows a detailed error with the cause and advice. For example, it may suggest setting worktree.baseRef to "head" in Claude Code settings, so worktrees start from your current commit.

Why

If worktree creation fails, the message now tells you what went wrong and what setting to change.

Read from
Names in the bundleworktree.baseRef
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up worktree.baseRef, on What's new. Also this week: **`worktree.baseRef`** chooses whether new worktrees branch from the remote default or local `HEAD`; **auto mode hard deny rules** block actions unconditionally regardless of allow exceptions; and **hooks see the active eff… whats-new/index see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up worktree.baseRef, on What's new.

See this entry in the whole of v2.1.299 →

Feedback