Skip to main content
Planning makes agents create a step-by-step plan before executing, improving accuracy on complex multi-step tasks.
The user asks a multi-step question; the agent creates a plan first, then executes each step.

Quick Start

1

Simple Usage

Enable planning with a single parameter — the agent drafts a plan before acting.
2

With Configuration

Use PlanningConfig to pick the planning LLM, tools, and approval behavior.

How It Works


Choosing Your Planning Mode


Configuration Options

Full list of PlanningConfig options, types, and defaults.

Common Patterns

Pattern 1 — Auto-approve a safe task

For low-risk, repeatable tasks, skip the review step and run the plan straight through.

Pattern 2 — Read-only research mode

Restrict the agent to reads during planning so it can investigate without side effects.

Pattern 3 — Separate planning LLM with tools

Use a cheaper model to draft the plan and give the planning phase its own tools.

Best Practices

Turn planning on with the default config before reaching for PlanningConfig. The default already separates drafting from execution, so you see the plan before it runs. Add config only when you need a different LLM or approval behavior.
Anything that writes files, sends messages, or makes API calls is hard to undo. Leave auto_approve=False for those tasks so the plan lands in front of you before any change happens. Reserve auto_approve=True for read-heavy or idempotent work.
Drafting a plan is lighter work than executing it. Set llm to a cheaper model (for example gpt-4o-mini) for the planning phase, and keep your stronger model on the agent for execution.
When you only need answers — not changes — set read_only=True. The agent can explore and report without the risk of writing or calling mutating tools during planning.

Planning Mode — the review and approval workflow in depth.

PlanningConfig — full options, types, and defaults.