Codex is brilliant at parallel tasks. Parallel is not a team.

Codex is a monster at a job I like.

You throw a pile of coding tasks at clouds you do not have to love. They run in parallel. They come back. You merge or you don't. Disposable is the point. If a cloud gets filthy, you kill it. That is good engineering manners.

Then someone says "we have a team of agents" because ten tasks ran at once.

They do not have a team. They have throughput.

Parallel tasks are still tasks

A team shares state.

A task is born, dies, and does not owe you next week.

Codex is optimized for the second thing. Many jobs. Isolated machines. Code as the artifact. When the cloud is gone, the job is gone, which is correct for a patch.

What is missing, on purpose:

• A standing backlog that is not the GitHub pile
• A teammate named Clerk who still exists when the PR is merged
• An invoice lane, an inbox, a calendar
• A way for Mail to wake Watch without you pasting a URL
• A cost picture that is "this lane, this week," not "this cloud, this burst"

I will not pretend invoices belong in a coding cloud. They do not. The error is using the thrill of parallel to stand in for ops.

Claude Code is the deep, local, session version of the same family. Codex is the parallel, disposable-cloud version. Both are session tools with extra horsepower. Neither is a shop.

What a team looks like when the work is not a repo

Tuesday morning is not a sprint board.

Clerk pulled seven late invoices and parked three. Mail drafted the routine replies and flagged a supplier. Maker's calendar is waiting for a no. Watch has a quiet card. Chief routed. You tap two things. The rest already happened.

That work is boring. It has to be boring. If it lives in a cloud you spin up when you remember, you will remember on the day cash is late.

Anthropic 2026: 57% of orgs on multi-stage workflows, 16% crossing teams. Parallel coding is a stage. Crossing teams is Clerk handing Watch a name. Microsoft 2025: 82% of leaders expecting digital labor to stretch capacity. Capacity in a small shop is not "more PR machines." It is "the reminder went out while I slept."

Compose

Keep Codex. I mean that.

When the work is a repo, use the factory. Parallel, disposable, ruthless.

When the work is a lane, put it on a teammate with a computer that stays up, own email, a vault, a gate. $99 is OSS models, that computer, a board. Bring ChatGPT, Claude, or Grok for the brain you already like. No per-task markup. Stack accounts. Fallback mid-task so a plan running dry does not kill the invoice run halfway. Dedicated workspace. We never train. Seven-day money-back. Dedicated VM for agencies: talk to us.

Maker might still kick a coding task at Codex the way a human developer would. That is composition. Clerk should never live in a cloud you plan to delete.

A cloud is not an address

This is the part people skip because the parallel demo is so pretty.

A disposable cloud cannot receive the customer's reply. It cannot hold a vault key the way a standing computer can. It cannot sit in Needs you overnight because you did not want it to send a refund note at 1 a.m. It cannot hand Watch a name after the PR merged, unless you built that glue, and then you are in the Hermes/OpenClaw business whether you said so or not.

So use the cloud for code.

Use a teammate for the rest:

• Clerk on unpaid invoices, weekday 9, stop before send
• Mail on the inbox, own address, drafts waiting
• Scout on the list you do not want to rebuild
• Watch on the thing that broke last month
• Chief to route so you are not pasting between clouds

$99 is still the computer, the board, OSS models. Bring the OpenAI plan if that is the brain you want on a lane. No per-task markup. Approvals. Dedicated workspace. We never train. Seven-day money-back.

It cannot do judgment, relationships, showing up, or taste. Codex cannot either. You keep those. The factory keeps the diffs.

Hermes is the closest thing to a native agent board you run yourself. Different trade: you babysit the box, or we do.

If your demo of "mission control" is ten coding tasks in flight and nothing in Needs you, you have a factory. Factories are great. They do not chase Bell & Rowe.