{"version":"2.1.222","anchor":"parked-agents-refuse-to-resume-into-a-worktree-that-vanished","canonical_anchor":"parked-agents-refuse-to-resume-into-a-worktree-that-vanished","heading":"Parked agents refuse to resume into a worktree that vanished","tier":"notice","area":"Worktrees","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/parked-agents-refuse-to-resume-into-a-worktree-that-vanished","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Parked agents refuse to resume into a worktree that vanished\n\nA parked agent refuses to resume if its worktree disappeared, instead of landing in the wrong directory.\n\n**What**\n\nResuming a parked or isolated agent verifies the recorded worktree first and refuses rather than silently landing somewhere else.\n\n**Details**\n\n- stats and verifies the recorded worktree and touches it\n- falls back to a covered directory only when the session's fences cover it\n- otherwise raises a terminal error saying the agent cannot be resumed\n\n**Evidence**\n\n`This agent cannot be resumed: its worktree`\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}