Workspace
Run multiple Codex sessions in parallel
Use Conductor workspaces to run several Codex tasks at once with separate branches, files, terminals, and review state
Use this guide when you want several Codex tasks moving at the same time without one task taking over another task's checkout.
In Conductor, the unit of independent Codex work is a workspace. Create one workspace for each task that should have its own branch, working tree, setup context, terminal, diff, and pull request path.
Codex also has native surfaces for local terminal work and app worktrees. Use Conductor when you want parallel Codex sessions plus Conductor's workspace sidebar, setup scripts, run scripts, diff review, checks, and pull request flow.
For the decision model, see Parallel agents. For upstream Codex behavior, see the official Codex CLI docs and Codex app worktrees docs.
Choose the unit of parallel work
Before you start more sessions, decide whether the work needs isolation or shared state.
Use separate workspaces when each Codex task should become its own branch, review, or pull request.
Use multiple chats in one workspace when the tasks need to share the same branch and current code state, such as one Codex session implementing while another reviews the same diff.
This choice matters more than the number of sessions. Parallel agents help when the tasks are independent enough to review separately.
Run several Codex tasks
Prepare the repository once
Add the repository to Conductor and make sure a new workspace can run the project.
Use Files to copy for static gitignored files such as .env.local. Use a setup script for commands that install dependencies, generate files, create symlinks, initialize local databases, or prepare other per-workspace resources. Use a run script for commands you want to start from the Run button.
Create one workspace per independent Codex task
Create a workspace with Command Shift N or the ... button next to New workspace.
Start from a GitHub issue, Linear issue, pull request, branch, or a new task. Conductor creates a separate git worktree and branch, then attaches the Codex chat, terminal, diff, and review state to that workspace.
Start Codex in each workspace
Open the workspace and choose Codex for the chat.
Give each Codex session a scoped prompt: what to change, what not to change, how to verify it, and when to stop for review. Repeat this for each independent task.
Run and test each workspace separately
Use the Run button or terminal from the workspace that owns the change. Setup and run scripts execute from the workspace directory.
If several workspaces need local servers at once, use CONDUCTOR_PORT so each workspace gets a separate port range. If your project cannot run cleanly from workspace directories, use Spotlight testing.
Review and merge workspace by workspace
Open the Diff Viewer with Command Shift D and inspect one workspace at a time.
Use the Checks tab to track git status, CI, deployments, comments, and todos. Merge and archive the workspaces that are ready; keep revising or archive the ones that are not worth shipping.
Keep the sessions coordinated
- Give each Codex session a task that can finish independently.
- Avoid assigning two workspaces the same file-heavy refactor unless you expect merge conflicts.
- Keep durable project context in
AGENTS.md, repository instructions, or the workspace.contextdirectory. - Use one workspace when the Codex sessions need to collaborate on the same in-progress branch.
Caveats
For the lower-level Git model behind this workflow, see Run Codex with Git worktrees. If you want the same workflow with Anthropic's agent, see Run multiple Claude Code sessions in parallel.