Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.260 ·

Worktree resume: distinguishing whether binding could actually be cleared

Resume now explains clearly when a worktree binding can't be cleared because transcripts are off.

TierYou'll noticehow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaWorktreeswhat it touches
KindBug Fixesin v2.1.260,
You'll notice

Resume now explains clearly when a worktree binding can't be cleared because transcripts are off.

When a resumed session's pinned worktree can't be verified and transcript saving is off, Claude Code now says so explicitly: "The worktree binding could not be cleared because transcript saving is off," and suggests using --fork-session or starting a new conversation instead of silently clearing or keeping the binding.

Read from
Names in the bundle--fork-session
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 --fork-session, on Error reference. When you fork a session, for example with [`--fork-session`](/docs/en/cli-reference#cli-flags) or [`/branch`](/docs/en/sessions#branch-a-session), Claude Code copies the original session's backups into the fork. When Claude Code can't copy… errors 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 --fork-session, on Error reference.

See this entry in the whole of v2.1.260 →