用三个 Codex CLI 终端搭建多智能体开发工作流：实现者、审查者与深度推理升级

After the GPT-6.1 Sol launch, both of my accounts got a usage reset. That pushed me to rethink my workflow because VS Code still didn't have the new model available, so I started using Codex directly from the CLI.

At first I opened two terminals, each running its own Codex session. I gave them different tasks in the same repository and explicitly told both of them that another agent was working in the repo, so they should avoid stepping on each other's toes.

After a while, I noticed something interesting: they actually seemed to be communicating/coordinating through an MCP tool.

That made me rethink the whole setup.

Now I'm experimenting with three parallel Codex terminals:

GPT-6.1 Sol Max Fast — Main Implementer Owns the implementation and makes the final decisions.

GPT-6.1 Sol Max — Reviewer Reviews the main agent's work, looks for mistakes, missing cases, architectural problems, and things the implementer may have overlooked.

Astra Max Fast — Deep Reasoning / Escalation Used when something is difficult, the implementation gets stuck, there is disagreement, or the problem needs significantly more reasoning.

The useful part is how I connect them.

I can run /status in one session, copy the relevant state/context into the main GPT-6.1 Sol session, and tell it: you are the main implementer; this is what your reviewer found.

Then the implementer can continue with that additional context. If the reviewer and implementer can't resolve something confidently, I escalate it to Astra.

So instead of using three powerful models independently, I'm trying to create a small engineering team:

Implementer → Reviewer → Deep-reasoning escalation

with one agent clearly owning the repository and the others supporting it.

For serious app development, this seems like a pretty good way to make steady progress. If you're working on a larger app or codebase, you can always try this kind of setup and see whether it helps you move faster while still keeping a second pair of eyes on the implementation.

I'm curious whether anyone else is building a similar multi-agent Codex workflow, especially using separate CLI sessions + MCP for coordination.