Repository navigation
feat: pick which repositories get a worktree in a multi-repo run, and add or remove them later - #352
Merged
LoganRupe merged 1 commit intoOct 20, 2026
Conversation
… add or remove them later An isolated run of a multi-repo project copied every repository, so a big assets repo was checked out on every task and a 70-repo polyrepo could not use worktrees at all. The worktree strategy takes `repositories`. Left-out repositories are linked into the run (or named by path when the run's root is itself a checkout), and agents are told they are shared checkouts to read but ask before changing. Above 8 repositories none gets a worktree unless named. A running thread can add a repository (worktree on its branch, setup script runs) or remove one (branch kept, refused while dirty). Web and mobile get pickers with a filter past 5 repositories. Claude Code keeps a resumed session's first system prompt, so a reopened Claude process now gets the current repository list in its first prompt. Multi-repo checkpoints run 8 at a time instead of 4.
Owner
Author
before-after.mp4 |
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
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.
Problem
In a multi-repo project, a new worktree copies every repository. A game repo with a big assets repo copies the assets on every task. A 70-repo polyrepo can't realistically use worktrees at all, so people work at the project root and lose per-repo diffs, commits and PRs. There was also no way to pull another repo into a thread once it had started.
Change
t3_thread_launchtakesrepositories.Known limit: a thread can't rewind to a turn from before a repo was added. This is noted in the user docs.
Scope and approval
Requested in the multi-repo projects discussion: choosing which repos get a worktree, telling the agent about the rest, and adding more later. This extends the existing multi-repo isolated runs on the fork's
multi-repo-workspacesbranch.Verification
Demo video (before/after, then web + iOS walkthrough):
repo-subset-demo.mp4
Written with Claude Opus 5.5 in Claude Code, running inside T3 Code.