Agent Orchestration
Hand a whole feature to a team of agents.
Describe what you want built. An orchestrator splits it into tasks and gives each one to the right agent and model. You see the plan and its cost before anything runs. Then it runs in parallel while you watch every agent's status.
How orchestration works →
Running 0
Waiting 0
Error 0
Done 1
✻ Project folder…User Stores and Motor…+
🏪
User Stores and MotorcyclesAdd a section where each user can open a virtual store to sell their cars…
Running · 1 of 10 tasks
ConsoleStop
The design task finished with a complete, additive plan for motorcycles and user stores that matches the remaining tasks, so the plan goes on unchanged. Expected total ($31.44) stays within the $46.03 budget.
Team plan
🧭
OrchestratorClaude Code · default model
📐
Feature ArchitectClaude Code · Opus 5.5~US$ 2.76
✓Map code and designUS$ 1.68
🗄️
Backend EngineerBash · npx tsc --noEmit…~US$ 9.26
Motorcycles schema and API~US$ 2.80 · ↳ 1
Store schema and API~US$ 3.30 · ↳ 1
Apply review fixes~US$ 3.16 · ↳ 2
🎨
Frontend EngineerClaude Code · Opus 5.5~US$ 12.24
Motorcycles in the UI~US$ 3.30 · ↳ 1
Store editor page~US$ 4.24 · ↳ 1
Public store pages~US$ 4.70 · ↳ 1
🔍
Code ReviewerCodex · GPT-5.5~US$ 5.92
Correctness review~US$ 3.77 · ↳ 1
Confirm fixes~US$ 2.15 · ↳ 1
Changes to the plan
Applied · 10:40 p. m.
The design task failed because its model needs usage credits this account doesn't have. I switched the architect to Opus 5.5 and retried the task; the rest of the plan is unchanged.
- Switches Feature Architect to Claude Code · claude-opus-5-5
- Retries “Map code and design”
Estimate~US$ 31.26
Tokens7M
SpentUS$ 3.12
Expected~US$ 31.62
BudgetUS$ 46.03
AI Mode: on◎ CodexPlan usage no data yet
Memory: 229 MB