Multi-repo support
What variant of Codex are you using?
App
What feature would you like to see?
Multi-repo context is the main reason some of us are still stuck in the CLI. In Claude Code you can point the assistant at multiple repos/directories and it “just works”, which makes cross-service changes, shared types, and platform work much faster.
Could we add something similar to Codex Mac/Web? A simple /add-dir (or “Add folder…”) capability that lets you attach additional directories outside the current repo to the session, with clear scoping/visibility (show what’s attached, remove/refresh, optional read-only). This would cover the common “two repos + shared lib + infra” workflows without having to drop back to the CLI.
If helpful, Conductor’s approach (conductor.build) is a decent mental model: explicit additional roots, then the agent can search/navigate across them when answering or making changes.
Additional information
_No response_
17 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Would love to see this, I'm using claude code app as my daily driver atm because it supports it
Would like this to be possible in the cloud as well, like "Add additional repo", such that it can work on one individual task across repositories, create individual branches and PRs for it.
+1 to this, would be a great!
+1 to this
+1 to this, would be amazing to preserve context when building with dependent repos!
+1 to this
+1 to this
+1 to this
+1 to this
+1
+1
This is currently the only blocker stopping me from making the switch from Cursor.
+1
You need to add the concept of workspace like Cursor did
+1
You need to add the concept of workspace like Antigravity did
This is biting me trying to develop some parallel workflows. I can't spin up a copy of my repo and start a thread in it to pick up later in codex desktop because of the hard requirement that one cwd === "project". It won't even show threads in subdirectories. Every single directory you want to see a thread in must be its own "project".
+1