CODEX FLEET

Codex Fleet

Jira for AI engineers. File a ticket, Codex picks it up, spawns sub-agents, and works the sub-tasks in parallel — every step on one board you can see, steer, and ship from.

01
TICKET
02
FLEET
03
SUB-TASKS
04
RUNNING
05
EVIDENCE
06
SHIPPED
01 · Ticket Filed
You write a ticket — feature, bug,
refactor — like you would in Jira.
02 · Fleet Assigned
Codex picks up the ticket and decides
which agents and sub-agents to launch.
03 · Sub-tasks Spawned
Codex breaks the ticket into sub-tasks,
spins up sub-agents, assigns each one.
04 · Agents Running
Watch every agent work in parallel —
logs, branches, attempts, retries live.
05 · Evidence Reviewed
Diffs, tests, screenshots, traces —
attached to every ticket and sub-task.
06 · Shipped
PR approved, merged, deployed,
ticket closed — no human paste-and-pray.
BOARD · LIVE12 TICKETS · 47 SUB-TASKS · 9 AGENTS WORKING
§ 01 · WHAT

Jira, but the assignees are AI.

A

Tickets, not prompts

File the work like you would in Jira — feature, bug, or refactor. Codex picks up the ticket and plans the rest.

B

Codex spawns sub-agents

Codex breaks the ticket down and launches a sub-agent for each sub-task. Watch them work in parallel, like employees.

C

Evidence on every card

Each sub-task carries its own diff, run-log, tests, and screenshots — attached to the PR before you review it.

D

Human still in command

Hold, re-assign, or kill any agent on any sub-task. Codex Fleet is built for control, not autopilot fantasies.

§ 02 · FLOW

From ticket to shipped, on rails.

Six lanes, one board. Every sub-task moves left to right — and you can stop, branch, or hand off any agent at any column.

01
TICKET
filed in plain language
02
FLEET
codex picks + assigns
03
SUB-TASKS
sub-agents spawned
04
RUNNING
branches + retries live
05
EVIDENCE
diffs + tests + traces
06
SHIPPED
PR merged + deployed
ticket
CF-4271 · checkout
CF-4288 · /api/teams 500
CF-4302 · react 19
CF-4310 · billing portal
sub-agent
codex-sub-a1
codex-sub-b2
codex-sub-c1
codex-sub-d3
branch
feat/payments-v3
fix/pool-exhaust
chore/upgrade-react-19
feat/billing-portal
status
RUNNING
REVIEW
EVIDENCE
DONE
evidence
12 tests · diff · log
6 tests · screenshot
diff · run-log.json
diff · changelog.md
§ 03 · BOARD

One ticket in.
A whole team of agents out.

File a ticket the way you would in Jira. Codex picks it up, plans the work, and spawns sub-agents that each open their own sub-tasks, branches, and PRs — every move visible on the board.

STATUSTODOASSIGNEDRUNNINGREVIEWEVIDENCEDONE
CF-4271PARENT TICKET

Rewrite checkout flow

picked up by codex-alpha · spawned 4 sub-agents
IN PROGRESS1/4 DONE
  • CF-4271·1
    Migrate payments API to v3
    RUNNING
  • CF-4271·2
    Rebuild order summary component
    REVIEW
  • CF-4271·3
    Add Stripe webhook + retries
    EVIDENCE
  • CF-4271·4
    Playwright e2e for happy path
    DONE
CF-4288PARENT TICKET

Bug: 500 on /api/teams under load

picked up by codex-beta · spawned 3 sub-agents
IN PROGRESS1/3 DONE
  • CF-4288·1
    Reproduce + add load test
    DONE
  • CF-4288·2
    Fix connection pool exhaustion
    RUNNING
  • CF-4288·3
    Add slow-query alerts
    ASSIGNED
BOARD · 2 PARENT TICKETS · 7 SUB-TASKSUPDATED 4S AGO
§ 04 · EVIDENCE

Review the work, not the agent.

Every sub-agent attaches diffs, tests, traces, and screenshots to its own sub-task PR. You approve with the same evidence you'd demand from a human teammate.

CF-4271·3·SUB-TASK OFCF-4271·feat/stripe-webhook

Add Stripe webhook + retries with exponential backoff

opened by codex-sub-a3 · attempt 3 of 5 · evidence verified
READY TO MERGE+412 / -88 · 14 files
CHECKS
  • unit · 184 passed
  • e2e · 12 passed
  • type-check
  • lint
ARTIFACTS
  • diff.patchVIEW →
  • run-log.ndjsonVIEW →
  • playwright-trace.zipVIEW →
  • screenshot-step-1.pngVIEW →
  • screenshot-step-2.pngVIEW →
GET STARTED

File a ticket. Watch the fleet work.

Open your first ticket. Codex picks it up, spawns sub-agents, and ships the first sub-task PR by tonight.

Start building