For developers and installing agents
Technical details, off the homepage.
The exact install path, requirements, fit, architecture boundaries, and links to the source of truth.
Stable installation
Install v0.3.0
Requirements: Codex with plugin and hook support, Git, and Python 3.10 or newer available as python on Windows or python3 on macOS and Linux.
Ask an agent
https://github.com/eyeinthesky6/codex-coordinator
Use the tagged marketplace release and install the plugin. Do not change my environment settings. Ask me only if Codex needs approval to trust the startup check.
Install manually
codex plugin add codex-coordinator@codex-coordinator
Review and trust the SessionStart hook when Codex asks. It reads small local coordination records, makes no network calls, and does not write project state.
No Codex app restart is required. Open a new Codex task after installation so it can load the plugin. There is no Coordinator service to start.
For an offline or development checkout, clone the repository and add its local directory as the marketplace instead. The README quick start remains the full installation source of truth.
First use
Say what you want finished.
Describe what you want finished here.
A suitable result is a short explanation of the work areas, clear owners, and one consolidated update when the project reaches a stable result. Coordinator normally targets one to three durable workers and treats five as the default ceiling.
Fair comparison
Use the smallest tool that removes the work you are doing by hand.
Separate Codex tasks may be enough when you are comfortable coordinating them yourself. Coordinator is useful when several durable tasks need ownership, recoverable handoffs, consolidated status, and one project-level result.
| Approach | Best fit | What it does not solve by itself |
|---|---|---|
| One Codex task | One coherent goal one agent can finish safely. | No parallel ownership is needed. |
| Parent-owned subagents | Short, bounded parallel help inside one task. | The parent still owns durable status, validation, and the final result. |
| Git branches or worktrees | Isolating file changes and Git history. | Who owns each job, what is blocked, and how handoffs survive restarts. |
| Separate Codex tasks | Several durable jobs you are happy to coordinate yourself. | You still reconcile ownership, status, handoffs, and the final result. |
| Codex Coordinator | Several durable Codex tasks working toward one repository outcome. | Git integration, product judgment, and important approvals remain yours. |
| Hosted project manager | Cross-team and cross-machine planning. | It adds a separate service and does not automatically understand Codex task ownership. |
Read the deeper fit and discovery guide for recommended and non-recommended cases.
Small by design
Zero third-party runtime dependencies
The shipped plugin uses Python's standard library. Beyond Codex, Git, and Python 3.10+, there is no orchestration framework, coordination daemon, database, queue, pip package, or npm package to install.
Mutable coordination state stays local. Only the repository discovery marker is intended to be committed. The plugin adds no separate coordination service and does not replace Codex or Git.
Optional local view
Mission Control is not required.
The core Coordinator works without a dashboard. Optional Mission Control separates queued work from work actually running, shows native task names and next actions, and keeps project state on your machine. It also uses only Python's standard library and runs only when you start it.
cd codex-coordinator
python -m apps.mission_control
See the Mission Control guide for background startup, Doctor behavior, settings, and stopping the local process.
Source of truth