workspace-level multi-repo support in Codex app

Resolved 💬 3 comments Opened Mar 19, 2026 by tlerbao Closed Apr 6, 2026

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What variant of Codex are you using?

app

What feature would you like to see?

Feature request: workspace-level multi-repo support in Codex app

I use Codex app for a full-stack project where frontend and backend are separate Git repositories under one parent workspace.

Current issue:

If I start Codex in the frontend repo, the agent can edit both frontend and backend files.
But the diff panel only shows changes for the current repo.
This makes cross-repo development harder to review and manage, even though the actual task often spans both repositories.

Why this matters:

Many real-world projects are split into multiple repos (frontend, backend, docs, shared packages).
A single product task often requires coordinated changes across repos.
VS Code / Cursor workspace can show multiple repositories together, but Codex app currently feels limited to a single repo view.

Requested improvement:

Add workspace support for parent directories containing multiple Git repositories.
Show diffs grouped by repository in one thread.
Allow separate Git actions per repo (status, branch, commit, worktree), while still treating the task as one workspace-level effort.
Optionally allow a thread to attach multiple repos explicitly.

Ideal UX:

Open a workspace like Next
Detect Frontend, Api, and Docs as separate repos
Let one agent work across them
Show a unified review panel with repo-separated diffs

This would make Codex much more practical for full-stack and monorepo-adjacent workflows.

Additional information

_No response_

View original on GitHub ↗

3 Comments

tlerbao · 5 months ago

Additional context from a real workflow:

My project is organized like this:

/Next/Frontend
/Next/Api
/Next/Docs

Frontend and Api are separate Git repositories, while Docs is shared project documentation.

In Codex app, if I start a thread in Frontend, the agent can still read and edit files in Api, which is useful for full-stack tasks. However, the diff/review panel only shows changes from the repo where the thread was started.

That creates a mismatch:

execution can span multiple repos
review visibility is limited to one repo

This is especially painful for tasks like:

adding a backend field and wiring it to frontend forms/tables
changing an API response and updating frontend types
adding a permission/menu on the backend and consuming it on the frontend

Expected behavior:

allow opening a parent workspace that contains multiple Git repos
detect and show all affected repos in one thread
group diffs by repo in the review panel
keep Git actions separate per repo (status, branch, commit, worktree)

This would make Codex much more practical for real full-stack development, where one feature often spans multiple repositories even if each repo remains independent.

github-actions[bot] contributor · 5 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#14218

Powered by Codex Action

Mozzarella123 · 5 months ago

yep, now it's unusable for multiple git repositories in one folder, switch back to Cursor
When i make any change after every follow up it clears previous changes -> i can't review overall conversation changed code