workspace-level multi-repo support in Codex app

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

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 ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗