Coordinate coding work through one Claude hub

A developer turned Claude into a control point for Claude Code and Codex, so they could spread work and usage across accounts.

Done with ClaudeClaude CodeCodex· Intermediate· Nov 2026

What they did
They made one Opus 5.5 chat the center of the setup and used it to direct other agent sessions from there. The developer works with it in a command-line environment and on a phone, while Claude frequently sends pieces of the job to Codex. They are also building a small CLI that can reach some agents through IRC.
How it went
That arrangement removed the need for heavier orchestration tools or agent platforms. The handoffs used to be about getting better output, but now they mainly help distribute token spending between Claude and Codex subscriptions. The IRC-based CLI has not been completed yet.
Tips
This model assumes you have access to both Claude and Codex, usually on higher-priced plans. It is easier to keep the setup manageable if you reserve delegation for tasks that do not need the main session's full attention.

Try it yourself with Claude

Help me design a coordinator setup for [project folder] where one Claude session manages other coding agents such as [Codex or another coding agent]. First, break my goal into [number] separate workstreams, say which ones should stay in the main session, and which ones should be sent out. Show me that plan and stop for my approval before you start any delegated session or do anything irreversible, including sending, deleting, submitting, or paying. When the agents finish, give me a combined report that says what each one did and flags any disagreements or unanswered items.

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.