Repository navigation
[Question] Is there a way to work with multi-repo projects? #1453
Description
I have a project that has multiple repositories, I work on them through vscode workspace so the agents can make changes across all repositories. Is there a way to work like this in T3Code?
I'm ready to dump Cursor horrible experience.
Ofc, I can add the parent folder containing all projects but then the git changes are not visible.
Activity
ercnshngit commentedon Mar 27, 2026
Yes, that would be great. For example, when using warp, if I'm in the main folder, it groups and displays all the changes and also shows the folders.
Ivorisnoob commentedon Mar 30, 2026
this is actually a good call, might try to convince them to add this
azimari-toure-ikbal commentedon Apr 20, 2026
I was looking for someone asking for the exact same feature. I'd love to have a group / workspace feature and have all my single repo in there and have the agents get the whole workspace context if needed and having the git changes visible.
CountableNewt commentedon Apr 22, 2026
Multiple repos in a project is something that Codex/CC Desktop/Cursor Glass haven't been able to get right and it's something that keeps me on legacy Cursor, definitely would love for this to be a feature
ORanuare commentedon Apr 22, 2026
Honestly, I don't get why almost all agent tools (besides Legacy Cursor) only support monorepos.
I’ve been using a custom skill to help agents see sibling projects, but it’s a bit of a headache when I’m working on a feature that spans across all of them. So instead of just knocking out one fully wired and tested change, I’m stuck making separate updates and then manually stitching them back together.
Apparently, the future of coding just doesn't involve multi-repos.
erenkulaksiz commentedon Apr 23, 2026
Hello, I have 2 different folders and different repos. I would like to work in them in the same chat (for example, frontend and backend) But at current state, I have to tell current agent to look up the project in my computer or start 2 chats where I could just open one.
func0der commentedon Jun 1, 2026
Since the same problem existed in OpenCode before, I was so annoyed that I threw a few tokens at the problem. This is the result: https://github.com/func0der/t3code/tree/feat/multi-repo-root
Since this project does not accept any contributions for new features right now, please test is yourself, if you want this :)
Let's gather feedback here, since I do not want to open a PR and get banned for annoying the devs ;)
LoganRupe commentedon Jun 26, 2026
Hey, figured I'd share since this thread's where the multi-repo stuff is at.
Been running a build locally for a while and it's working really well day-to-day. A project is defined by a
.code-workspacefile (same one VS Code uses), so repos can be arbitrary paths: cousins in different trees, no shared parent needed. T3 resolves thefolders[], treats the git ones as roots, and the diff view shows changes grouped per repo while the agent edits across all of them in one thread. Single-repo projects work exactly like today.It lives on my fork if anyone wants to poke at it:
LoganRupe/t3code @ multi-repo-workspaces.Big thanks to @func0der for the
feat/multi-repo-rootbranch, that's where the data foundation came from.Not pushing for a PR, just sharing in case it's useful to anyone else here, and to say thanks for the original work.
stefanvandervelden-zipline commentedon Aug 7, 2026
The lack of multi-repo support is basically preventing me from being able to really use T3 Code at work. I'm loving it for personal projects that are contained to a single repo, especially the per-turn diffs, if multi-repo support was added I would switch to T3 Code at work immediately! For now I'm stuck in the Claude Code TUI 😅
LoganRupe commentedon Aug 7, 2026
Hi @stefanvandervelden-zipline - if you're willing to build/package yourself, my fork provides multi-repo support: LoganRupe/t3code @ multi-repo-workspaces. The build scripts are in the
package.json. Feel free to raise issues on my fork, happy to address them. I try to rebase off this upstream every few days and grab the latest changes.NOTE: The reason I haven't submitted a PR for this is because it's against their
CONTRIBUTING.mdatm. This is a large feature.stefanvandervelden-zipline commentedon Aug 7, 2026
Oh that's awesome @LoganRupe! I wasn't sure how much work you were planning to put into maintaining that fork, so didn't want to jump straight into it at first. I'll definitely make sure to report anything I find! Thanks for the fork, hopefully you don't have to maintain it for too long!
stefanvandervelden-zipline commentedon Aug 7, 2026
@LoganRupe your fork seems to have github issues disabled, I believe that's just the default for forks, and I think you can just enable issues in the repo settings? I've already encountered one thing that might be worth fixing, and I noticed that I couldn't actually post an issue 😅
Seems to be working so far though! Haven't done much with it just yet though (been busy)
LoganRupe commentedon Aug 7, 2026
Allowed issues now. Ta. 👍
CDVolvik commentedon Aug 10, 2026
Same use case keeps coming up: a project root with multiple nested git repos under it (VS Code multi-root / workspace style). Opening the parent works for the agent, but git / diffs / worktree features don't treat the child repos as roots.
If you're hitting this, please don't open a new issue — 👍 this one and drop a short note with your layout (parent path + how the nested repos are arranged). Signal helps more than duplicates.
Stopgaps people are already using (not official, not a PR into main — CONTRIBUTING is still cool on large features):
Would love first-class multi-repo roots in upstream whenever the team is ready for it.
alanbem commentedon Aug 13, 2026
Yup, my use case as well.
I need to work with multiple repositories. They are in different progress of agentification, so I created workspace directory - that contains those repos - where I setup my agentic context, docs & skills. Agent can work on single or multiple repos at once depending on the scope.
Would love to have such support in T3 Code
none23 commentedon Aug 14, 2026
Here's what I would suggest.
That preserves git history across all your repos and works with every tool I've used.
An agent should be able to set it up for you easily.