Let Codex implement while you handle planning

One person used ChatGPT for planning and Codex for execution, with a small port helper to keep parallel local runs from colliding.

Done with Codex· Intermediate

What they did
The commenter split the work between two agents: ChatGPT shaped the approach, kept the versioning rules straight, and drafted the next instruction, while Codex handled the coding. They moved text back and forth by hand in long, extended-thinking conversations. In a separate setup, they also used a tiny tool called portbroker so an agent could find an open port, record it, and place it into $PORT automatically.
How it went
They said this reduced prompt drift and made local multi-agent work feel steadier and easier to predict. The tradeoff was the manual copy-paste loop, along with slowdown as threads grew long enough to turn to “sludge,” sometimes forcing a fresh session.
Tips
This works best when one agent owns the plan and another owns the edits, with a human checking the handoff. If you keep a port-reserving helper in the loop, make sure it only sets up the environment and pauses before anything destructive or irreversible.

Try it yourself with Codex

I’ve drafted a plan for [task] in [repo path or project name]: [paste the plan or link to it]. Follow it with minimal back-and-forth, and if you need to run any server, test, or local process that depends on a port, first reserve a free one, log it, and place it into [env var or config field] so parallel runs do not conflict. Work through the implementation, then give me a concise summary of the changes and the checks you completed. Before you push, delete, submit, or make any other irreversible change, stop and ask for my approval.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.