Roles & Orchestration
Promote your workflows into reusable roles, run as foreground subagents under the CoA.
Introduced at Warp 3. You stop running one agent and start running a small team — each a specialized role with its own workflows. The orchestration is deliberately simple: foreground subagents, launched and collected by the Chief of Agents, with no back-channel between them.
Role files for multi-agent work
Consolidate the workflows and checklists you built at Warp 2 into roles. Different roles get different workflows — an Engineer differs from a blog writer; a Growth Engineer does outcome engineering, code and content that leads to sales. A role file is just durable, reviewable instruction, like everything else the forward-deployed agent writes.
Foreground subagents under the CoA
Roles run as foreground subagents launched by the Chief of Agents. There is no inter-agent messaging — each subagent runs to completion and returns its report. That means you must front-load each subagent's full instructions: you cannot message it mid-run to course-correct.