Skip to main content
Multi-Agent Planning generates a high-level plan before distributing tasks across agents, improving coordination on complex workflows.
The user defines tasks; a planning LLM drafts a plan before agents execute.

Quick Start

1

Simple Usage

2

With Reasoning


Single-Agent vs Multi-Agent Planning

PlanningConfig plans within a single agent’s execution. MultiAgentPlanningConfig plans across multiple agents and tasks.

How It Works


Multi-agent planning (MultiAgentPlanningConfig) generates plans at the orchestration level — it decides what tasks to run and which agents run them.This is different from single-agent PlanningConfig (see Planning Mode), which makes a single agent break down its own task into steps before acting.

Configuration Options

Full list of options, types, and defaults — MultiAgentPlanningConfig

Common Patterns

Pattern 1 — Automated multi-agent research pipeline


Best Practices

Planning requires understanding the goal and decomposing it into tasks. Use gpt-4o, claude-3-5-sonnet, or similar capable models. Smaller models often produce poor plans.
In automated workflows where human review isn’t possible, set auto_approve=True. In interactive applications, leave it False so users can review and adjust the plan before execution.
reasoning=True adds chain-of-thought prompting to the planning step, helping the planning model think through dependencies and edge cases before producing the task list.
Use multi-agent planning when you have a team of specialized agents and a complex goal that needs task decomposition. Use single-agent planning (via PlanningConfig) when a single agent needs to break down its own sub-goal.

Planning Mode

Single-agent planning configuration

Multi-Agent Execution

Configure iteration and retry limits

Multi-Agent Hooks

Intercept task lifecycle events

Autonomous Workflow

Fully autonomous multi-agent pipelines