{"version":"2.1.222","anchor":"agent-records-remember-that-their-worktree-was-cleanly-remov","canonical_anchor":"agent-records-remember-that-their-worktree-was-cleanly-remov","heading":"Agent records remember that their worktree was cleanly removed","tier":"notice","area":"Worktrees","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/agent-records-remember-that-their-worktree-was-cleanly-remov","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Agent records remember that their worktree was cleanly removed\n\nResuming an agent whose worktree you deliberately removed no longer warns about missing worktree state.\n\n**What**\n\nAn 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.\n\n**Details**\n\n- Agent metadata gained `worktreeCleanlyRemoved: !0`, written at the point the worktree is removed\n- The flag is inherited from the parent agent record, so child agents do not re-trigger the warning\n- Consulted on resume, and suppresses the `git_worktree_resume_binding_missing` telemetry event\n- Applies to everyone, no gate\n\n**Evidence**\n\n`worktreeCleanlyRemoved`\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}