You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
WorktreesArea: what it touches
Bug FixesKind: in v2.1.222,
Bug FixesSection of the release
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.
