Quick Start
1
Enable Planning
2
With Configuration
How Planning Works
The Planning Process
Configuration Options
Non-interactive environments
Plans auto-approve in non-interactive environments. When
stdin is not a TTY — CI runners, cron jobs, Docker containers, GitHub Actions, or piped scripts — the default approval handler automatically approves every plan and execution continues. In an interactive terminal, the agent still prompts as before.Planning Modes
Simple Planning
Configured Planning
Read-Only Planning
Multi-Agent Planning
Enable planning for multi-agent workflows:When to Use Planning
✅ Use Planning For
- Complex multi-step tasks
- Tasks requiring coordination
- Code refactoring projects
- Research and analysis
- Content creation workflows
❌ Skip Planning For
- Simple Q&A
- Single-step operations
- Real-time responses needed
- Trivial tasks
Best Practices
Use a powerful model for planning
Use a powerful model for planning
Planning benefits from stronger reasoning. Use
gpt-4o or similar for planning even if using a smaller model for execution.Enable reasoning for complex tasks
Enable reasoning for complex tasks
Set
reasoning=True to see the agent’s thought process and catch issues early.Review plans before execution
Review plans before execution
Keep
auto_approve=False for critical tasks to review and modify plans.Use read-only mode for analysis
Use read-only mode for analysis
When analyzing code or data, use
read_only=True to prevent accidental modifications.Related
Reflection
Self-evaluation after execution
Autonomy
Control agent independence

