Skip to main content
Planning enables agents to think before acting - decomposing complex tasks into manageable steps, then executing them systematically.

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.
Force explicit approval everywhere (e.g. fail CI instead of auto-approving):

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

Planning benefits from stronger reasoning. Use gpt-4o or similar for planning even if using a smaller model for execution.
Set reasoning=True to see the agent’s thought process and catch issues early.
Keep auto_approve=False for critical tasks to review and modify plans.
When analyzing code or data, use read_only=True to prevent accidental modifications.

Reflection

Self-evaluation after execution

Autonomy

Control agent independence