Plan with task graphs
Runs persist a dependency-safe DAG instead of a flat checklist, so coordination, sequencing, and parallelism are explicit.
Open Source Multi-Agent Delivery
Multi-Agent Delivery Control Plane
A workflow-oriented API, supervised worker runtime, and operator interfaces for planning, dispatch, review, governance, and publish handoff.
- Model repositories, runs, task DAGs, approvals, validations, artifacts, and audit exports directly.
- Dispatch Codex-backed work into isolated worktrees with recovery-aware worker supervision.
- Keep blockers, evidence, policy posture, and branch or PR handoff in one operator loop.
- Workflow-oriented API
- Isolated worktrees
- Dependency-safe task graph
- Audit-ready evidence
Operator Proof
- 07 shipped browser surfaces
- 06 operator loop phases
- OSS docs, guide, and journey included
Operator Loop
From repository trust to publish handoff.
Codex Swarm is built around a concrete operating sequence, not a pile of disconnected AI sessions. Each phase keeps context, evidence, and ownership intact.
-
01
Onboard
Attach provider, workspace, trust, and policy posture to a repository before work starts.
-
02
Define Run
Create a delivery goal with branch context, concurrency budget, and a dependency-safe task graph.
-
03
Dispatch
Route slices across Codex-backed agents and supervised workers in isolated worktrees.
-
04
Monitor & Review
Track blockers, approvals, validations, artifacts, and transcript context from one board-first workspace.
-
05
Govern
Confirm retention, provenance, policy posture, and audit evidence without digging through raw storage.
-
06
Publish Handoff
Attach branch publish status, PR metadata, or manual handoff artifacts when the run is ready to leave the control plane.
Why Codex Swarm
AI delivery needs an operating model, not session sprawl.
The failure mode in AI-assisted software delivery is fragmentation: flat task lists, invisible approvals, stray artifacts, and no reliable handoff state. Codex Swarm treats those as first-class workflow concerns.
Treat evidence as product state
Approvals, validations, artifacts, and audit exports are modeled directly, so review and governance survive beyond chat transcripts.
Supervise real execution
Workers materialize isolated worktrees, launch Codex sessions, track thread state, and surface recovery clues when slices stall.
Keep handoff visible
Branch publish and PR handoff are part of the run contract, which makes delivery posture inspectable instead of implied.
Core Capabilities
The control plane is opinionated where delivery risk actually lives.
Codex Swarm ships the primitives operators need to plan, supervise, recover, and prove software delivery. The system stays grounded in repositories, runs, workers, and evidence rather than generic assistant abstractions.
Workflow-first control plane
Repositories carry provider, trust, and policy metadata while runs, tasks, and handoff state stay anchored to delivery reality.
Codex-backed execution
Supervised workers handle worktree provisioning, Codex session launch, validation execution, and recovery-aware placement.
Operator interfaces
Browser surfaces cover projects, project runs, automation, run board, lifecycle, and settings while the TUI supports terminal-heavy operation.
Governance and evidence
Validation status, approval provenance, artifact retention, and audit exports remain visible throughout the operating loop.
Control Surface Signals
- Dependency-safe task DAG
- Recovery-aware workers
- Board-first run workspace
- Review and approval visibility
- Audit export evidence
- PR or branch handoff tracking
Product Surfaces
Real interfaces for the real operator loop.
The repository already ships concrete browser surfaces, not just architecture diagrams. Run Board and Run Lifecycle are the deepest proofs because they expose active operation, diagnostics, and recovery context directly.
The board prioritizes task execution first, with blockers and diagnostics close enough to act on without losing flow.
Lifecycle centralizes placement, transcript context, recovery clues, and recent events when a slice needs intervention.
Technical Foundation
Open source delivery infrastructure with a credible runtime shape.
Codex Swarm is a working open source product with a modular repository layout, operator materials, and a concrete local bootstrap path.
Stack
Repo Shape
- apps/api for control-plane API, persistence, governance, and scheduling
- apps/worker for worktree provisioning, Codex supervision, and validation execution
- frontend for projects, runs, automation, lifecycle, review, and settings surfaces
- apps/tui for terminal workflows and capture-oriented operator views
- shared packages for contracts, orchestration, and database support
Quick Start
corepack pnpm install
cp .env.example .env
corepack pnpm dev:api
corepack pnpm dev:worker
corepack pnpm dev:frontendOpen Source Control Plane
Inspect the repo. Read the operating docs. Start shaping governed delivery.
Codex Swarm is already opinionated about repositories, runs, workers, evidence, and publish handoff. The fastest way to evaluate it is to inspect the repo, trace the operator journey, and read the product docs side by side.
