Quick Start
1
Simple Usage
2
With Configuration
Which Approval Mode Should I Use?
Pick how much control you keep over the plan before it runs.How It Works
The final step restores your original tasks so
team.tasks is exactly what you passed in.
Inspecting the plan after execution
Your original tasks stay canonical after a planned run — the plan-derived steps are kept separately for introspection. Whenplanning=True on PraisonAIAgents(...), the original tasks you passed in are preserved and remain the canonical team.tasks after .start() returns. The plan-derived intermediate steps are kept for introspection under team._plan_tasks, and task_id_counter is advanced past the max original id so any later team.add_task(...) calls do not collide.
Fixed in PraisonAI PR #4034 — previously
team.tasks was overwritten with the plan-derived tasks and the originals were lost. If you have code that reached into team.tasks[0] after a planned run expecting to see the auto-plan, that code needs to read team._plan_tasks now.Configuration Options
Common Patterns
Read-only planning
Auto-approved pipeline
Multi-agent with planning
Best Practices
Use planning for complex multi-step tasks
Use planning for complex multi-step tasks
Planning shines when the path to a solution is unclear. For simple one-step tasks, direct execution is faster.
Enable read_only for safe exploration
Enable read_only for safe exploration
Set
read_only=True when the agent should research code or documents without risk of modification.Provide research tools during planning
Provide research tools during planning
Pass
tools=[search_web, read_file] so the planning phase has relevant context.Enable reasoning for complex requests
Enable reasoning for complex requests
Set
reasoning=True for chain-of-thought analysis in the plan.Related
Workflows
Create reusable multi-step workflows
Hooks
Intercept agent behaviour at lifecycle points

