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

Agent records remember that their worktree was cleanly removed

You'll notice
Useful3 Signal0
Worktrees

Resuming an agent whose worktree you deliberately removed no longer warns about missing worktree state.

What

An isolated agent whose worktree was deliberately removed no longer warns on resume that the worktree "is not recorded for this isolated agent". The removal is recorded in the agent's metadata instead of looking like missing state.

Details
  • Agent metadata gained worktreeCleanlyRemoved: !0, written at the point the worktree is removed
  • The flag is inherited from the parent agent record, so child agents do not re-trigger the warning
  • Consulted on resume, and suppresses the git_worktree_resume_binding_missing telemetry event
  • Applies to everyone, no gate
Evidence

worktreeCleanlyRemoved

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 →