Quick Start
User Interaction Flow
Process Enum
Process Types
| Type | Description | Use Case |
|---|---|---|
Sequential | Agents run one after another, each receiving previous output | Pipelines, step-by-step workflows |
Parallel | Agents run concurrently on the same task | Multi-perspective analysis, speed |
Hierarchical | Manager delegates to workers | Complex coordination, validation |
AgentTeam
Builder Methods
| Method | Signature | Description |
|---|---|---|
new() | fn new() -> AgentTeamBuilder | Create builder |
agent(a) | fn agent(self, Agent) -> Self | Add agent |
process(p) | fn process(self, Process) -> Self | Set process type |
verbose(b) | fn verbose(self, bool) -> Self | Enable logging |
build() | fn build(self) -> AgentTeam | Build team |
Runtime Methods
| Method | Signature | Description |
|---|---|---|
start(task) | async fn start(&self, &str) -> Result<String> | Run team on task |
run(task) | async fn run(&self, &str) -> Result<String> | Alias for start |
len() | fn len(&self) -> usize | Number of agents |
Sequential Process
Each agent runs in order, receiving the previous agent’s output as context:Parallel Process
All agents work simultaneously on the same input, results are combined:Best Practices
Use Sequential for dependent steps
Use Sequential for dependent steps
When each agent needs the previous agent’s output - research → write → edit.
Use Parallel for independent analysis
Use Parallel for independent analysis
When agents can work simultaneously - multiple perspectives, speed optimization.
Enable verbose for debugging
Enable verbose for debugging
Use
.verbose(true) to see workflow execution details.Keep teams focused
Keep teams focused
3-5 agents typically works well. Split larger workflows into multiple teams.

