Building Workforces
A workforce is a manager agent plus a set of worker agents. The aim is not a rigid flowchart but a strong team structure that adapts at runtime. This page walks through assembling one.
Before You Start
- A capable, broad agent to act as the manager.
- Worker agents with clear, narrow roles.
- Models configured for the manager and workers, plus any knowledge bases and tools they need.
Choose the Manager
The manager breaks down requests, decides which worker should act, combines intermediate results, and handles ambiguous or cross-domain tasks. Good managers are broad, structured, and careful about delegation.
Add Workers
For each worker, define the source agent to reuse, an alias, and assignment instructions describing what it should focus on. A typical research team:
| Worker | Responsibility |
|---|---|
| Researcher | Gather sources and summarise findings. |
| Analyst | Structure comparisons and identify patterns. |
| Writer | Turn results into a final narrative. |
Generate from a Prompt
You can also bootstrap a workforce from a description — state the team goal, the manager role, and each worker's responsibility. Treat the generated result as a first draft and refine it.
Refine with the Builder
The builder supports a propose / apply flow, so you can iterate on team structure — adding or removing workers, reassigning responsibilities, or changing manager instructions — without rebuilding by hand. For the underlying endpoints, see the Workspace API.
Publishing Lifecycle
Workforces move through draft → active → archived. Iterate in draft, publish once the structure is stable, and unpublish to move an active workforce back to draft for further changes.
Keep teams small
Start with one manager and two to four workers with crisp boundaries. Too many workers make delegation noisy — add specialists only when a real need appears.
Next Steps
- Workforces → — concepts and orchestration
- Building Agents →
- Tools & Skills →