Planners

Plan Strategies

Choose when to plan deeply, when to stay direct, and when to keep routing deterministic.

Overview

Planners are useful only when the request actually needs decomposition. Overseer now classifies work first so not every task becomes a planning exercise.

Operator Note

Overseer works best when each layer stays explicit: the orchestrator routes, supervisors execute, tools return evidence, and traces show what actually happened.

Getting Started

Use planning for multi-step work with dependencies, not for short conversational requests.

Configuration

Keep planner outputs structured so the orchestrator can hand clean step definitions to supervisors.

Examples

plan.json

{
  "mode": "multi_step",
  "steps": [
    "inspect the request",
    "route to the right supervisor",
    "synthesize the final answer"
  ]
}

Next Steps

Continue with Workflow Basics or head back to the documentation home.