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.All PlanningConfig fields
All PlanningConfig fields
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
Start with planning=True
Start with planning=True
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.Keep auto_approve=False for irreversible actions
Keep auto_approve=False for irreversible actions
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.Use a cheaper planning LLM
Use a cheaper planning LLM
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.Reach for read_only on investigations
Reach for read_only on investigations
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.Related
Planning Mode — the review and approval workflow in depth.
PlanningConfig — full options, types, and defaults.

