Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.222 Home All releases ←olderv2.1.221 v2.1.223newer→
Claude Code v2.1.222

Resuming into a missing or unverifiable worktree is now explained

You'll notice
Useful4 Signal0
Worktrees

Resuming into a missing worktree now warns you, and headless runs exit with an error instead of continuing.

What

Worktree re-entry on resume returns a structured outcome that the session reports, instead of quietly continuing without isolation.

Details
  • a vanished worktree clears the binding and continues without isolation
  • an unverifiable or rejected pin keeps the binding
  • interactive sessions show a warning message; headless and print paths write an error to stderr and exit non-zero rather than continuing unisolated
  • telemetry tengu_worktree_resume_root_rejected carries the reason and a poisoned flag
Evidence

The worktree binding has been cleared.

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.222 →