{"version":"2.1.203","anchor":"agent-isolation-refuses-to-run-after-worktree-removed","canonical_anchor":"agent-isolation-refuses-to-run-after-worktree-removed","heading":"Agent Isolation: Refuses to Run After Worktree Removed","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.203\/e\/agent-isolation-refuses-to-run-after-worktree-removed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.203","markdown":"### Agent Isolation: Refuses to Run After Worktree Removed\n\nWhen an isolated agent's worktree has been removed externally and the only fallback would be running in the parent session's shared checkout, the agent now refuses to run and reports the problem:\n\n\"This agent is isolated in the worktree `<path>`, but its working directory `<cwd>` no longer exists and the only recovery target is the parent session's shared checkout. Refusing to run there \u2014 the isolation worktree appears to have been removed. Report this instead of retrying.\"\n\nPreviously the agent might silently run commands in the parent directory.\n\n**Evidence**\n\nIsolation safety check (search for `\"Refusing to run there \u2014 the isolation worktree appears to have been removed\"`)"}