fix(server): recover pruned thread worktrees - #29
Merged
Merged
Conversation
github-actions
Bot
added
vouch:trusted
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A restart can prune a merged thread worktree while a queued follow-up still references it. The provider then respawns in a missing cwd and leaves the thread failed.
Recreate missing T3-managed worktrees before provider startup, using the latest ready checkpoint when the local branch was pruned. Recovery reruns the project setup script and refuses to reuse a branch checked out by another worktree.
Verified with 53 focused ProviderCommandReactor tests, server typecheck, and targeted lint.
Model: GPT-5.6-Sol
Harness: Codex via T3 Code