Strong fit
- Implementation followed by independent review.
- A usage limit or reliability issue blocks the current Agent.
- A long task with a clear phase boundary.
Multi-Agent workflow
Switch Agents. Keep the project.
Let Codex finish one part of the job. Then open Claude Code on the same files, for a second opinion, a different approach, or because Codex hit its usage limit. What carries over is what you can check: files, diffs and test results.
- Shared project files
- Separate Sessions
- Reviewable handoff
01 · Working evidence
Same files. Separate chats.
Files, diffs, test results, previews and the decisions you signed off on carry from one chat to the next. Each Agent still works its own way.01CodexShared project files
02HandoffSeparate Sessions
03Claude CodeReviewable handoff
Give each Agent its own chat and its own part of the job. Let the files and test results carry the handoff.
Open a shared Workspace02 · Workflow
A practical Codex-to-Claude Code handoff
Give each Agent a bounded role and make the saved project state the evidence both must inspect.- 01
Codex implements
Define the outcome, ownership, protected files, and checks. Save the changed files, diff summary, commands, and open risks.
- 02
A person inspects
Review the current files and Preview, then write a concise handoff with goal, state, checks, risk, and next action.
- 03
Claude Code reviews
Start a separate Session, verify the handoff against the files, and continue only within the assigned boundary.
03 · Task fit
Use two Agents when the phase boundary adds value
Implementation followed by an independent review is stronger than two Agents editing the same files without ownership.Not the right fit
- Two Sessions editing the same files without coordination.
- A tiny task where handoff costs more than it saves.
- A workflow expecting access to another Agent's private reasoning.
04 · Boundaries
The Workspace preserves artifacts, not assumptions
The next Agent should verify the current files and checks rather than trusting a transcript summary.- 01
Separate Sessions can still create conflicting edits.
- 02
Agent.Space does not automatically resolve semantic merge conflicts.
- 03
The live selector governs compatible models and controls for each Agent.
06 · Questions
Working with two Agent harnesses
Keep the shared and separate parts of the workflow clear.Separate Sessions in the same Workspace can work from the current saved project files. Inspect the latest state before each handoff.
No. Preserve important context in files, validation output, approved decisions, and a concise handoff note.
Yes, when ownership does not overlap. Simultaneous edits to the same files can conflict and need deliberate integration.
Not necessarily. Agent harness and model are separate choices. Use combinations shown in the live Workspace.
Right now
New Agent. Same project.
Give each Agent its own chat and its own part of the job. Let the files and test results carry the handoff.