{"version":"2.1.281","anchor":"remote-control-worktree-cleanup-keeps-worktrees-whose-checko","canonical_anchor":"remote-control-worktree-cleanup-keeps-worktrees-whose-checko","heading":"Remote Control worktree cleanup keeps worktrees whose checkout moved or could not be checked","tier":"notice","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-control-worktree-cleanup-keeps-worktrees-whose-checko","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote Control worktree cleanup keeps worktrees whose checkout moved or could not be checked\n\nRemote Control cleanup now keeps a worktree if its checkout moved or Claude Code could not check it for changes\n\n**What**\n\nA worktree is a separate working copy of your project. When a Remote Control session tears down its worktree, it now keeps it in two cases:\n\n- The checkout moved.\n\n- The check for changes failed, labelled \"could not check for changes\".\n\nShutdown cleanup also passes a read deadline. When the logged id differs from the real work id, `stopWork` logs a redacted error showing only the status or the error name.\n\n**Why**\n\nFewer worktrees are removed at teardown, so a worktree Claude Code could not check is left for you to look at.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}