{"version":"2.1.281","anchor":"exitworktree-reports-a-fallback-directory-when-the-original","canonical_anchor":"exitworktree-reports-a-fallback-directory-when-the-original","heading":"ExitWorktree now reports where the session ended up when the original folder is gone","tier":"notice","area":"Worktrees","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/exitworktree-reports-a-fallback-directory-when-the-original","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### ExitWorktree now reports where the session ended up when the original folder is gone\n\nExitWorktree results now include restoredCwd and originalCwdMissing and say which folder the session moved to if the original was deleted\n\n**What**\n\nA worktree is a separate copy of your project's files that Claude can work in, and `ExitWorktree` is the tool Claude uses to leave one. Its result now includes two more fields, `restoredCwd` and `originalCwdMissing`, which record which working directory (the folder the session runs in) the session went back to.\n\n- The fields appear both when exiting normally (\"Exited worktree. Your work is preserved at \u2026\") and when the worktree could not be removed (\"Exited worktree but could not remove it\").\n\n- If the original folder no longer exists, the result says so and names the folder the session moved to instead, for example \"The original directory \u2026 no longer exists, so the session is now in \u2026\".\n\n- It may also suggest restarting Claude from a folder that exists.\n\nThe tool's stock description was not changed in this release.\n\n**Why**\n\nBefore, a session could end up in an unexpected folder after leaving a worktree without any notice. Now both Claude and you are told where the session actually is.\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}