Claude Code v2.1.222 ·
Resuming into a missing or unverifiable worktree is now explained
Resuming into a missing worktree now warns you, and headless runs exit with an error instead of continuing.
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
WorktreesArea: what it touches
ImprovementsKind: in v2.1.222,
What probably matters to youSection of the release
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.
See this entry in the whole of v2.1.222 →
