Does Codex Coordinator use more tokens?

Running several agents usually uses more tokens than one comparable task. Coordinator does not bypass normal Codex plan, usage, token, or concurrency limits.

No. You can explicitly ask Coordinator to split and coordinate a suitable goal. Your normal Codex plan, model, usage, and concurrency limits still apply.

Does Codex Coordinator replace Git worktrees?

No. Worktrees isolate branches and files. Coordinator handles task ownership, handoffs, status, and consolidation.

Frequently asked questions

Straight answers before you install.

Q: Is Mission Control required?

No. The core Coordinator works without Mission Control. Mission Control is an optional local dashboard that runs only when you start it.

What it does, why we made it, what it costs in tokens, and where its responsibility ends.

What does Codex Coordinator do?

It helps several Codex tasks work on different parts of one project. It remembers what each task is doing, checks when work may overlap, and brings everything back into one clear update.

Why did you make it?

Because several Codex tasks can create a second job for you: checking every chat, copying updates between tasks, spotting duplicated work, and rebuilding the plan after a pause. Coordinator carries that work while you stay in control of the result and important decisions.

Does it use more tokens?

Usually, yes. Several Codex tasks normally use more tokens than one similar task. Coordinator still follows your normal Codex plan and limits. The benefit is less repeated work and less time spent managing tasks—not a promise of lower token use.

Is Mission Control required?

No. Coordinator works without it. Mission Control is an optional local dashboard that shows what is working, what needs you, and where 2 tasks may be changing the same files. It runs only when you start it.

Do I need Ultra? What about subagents?

You do not need Ultra. Subagents are still useful for short help inside one Codex task. Coordinator is useful when several separate Codex tasks need to stay organised and return one combined result.

Does it replace Git worktrees?

No. Worktrees separate branches and files. Coordinator tracks who owns each job, what is blocked, what survived a restart, and what still needs review. They solve different problems and can be used together.

Does it send my code to another server?

No extra Coordinator server is added. It uses your normal Codex tasks and small files stored with the project on your computer. Its startup check makes no network calls. Codex itself still uses the normal Codex service and account you already use.

Can agents overrule me?

No. Coordination does not turn a suggestion into permission. Publishing, deployment, database changes, environment changes, and other important actions still follow your instructions and existing approval boundaries.

Do I need to restart Codex or start Coordinator?

You do not need to restart the Codex app or run a Coordinator service. After installation, open a new Codex task so it can load the plugin. Then describe the result you want. Mission Control is separate and runs only if you choose to open the dashboard.

Is it in OpenAI’s Plugin Directory?

Not currently. Today you install it from this project’s GitHub marketplace package. That package is ready for Codex agents and people to install using the steps on the homepage.

When should I avoid it?

Use one Codex task for one clear job. Use subagents for quick help inside that task. Add Coordinator when several separate Codex tasks would otherwise make you copy context, check progress, and combine the answers yourself.

What does it require?

Codex with plugin and hook support, Git, and Python 3.10 or newer. The shipped plugin has zero third-party runtime dependencies. See the Developers guide for the full installation and technical comparison.