Planning settings
By the end of this page you will know what every control in the configuration panel changes, and which ones are worth touching first.
Prerequisites
- A Planner / Executor system with at least one member (Your team).
- Admin or Developer role.
The panel is organised as numbered groups, in the order a turn actually happens. This page follows the same order.
2. Handling a turn
Before anything runs, one quick check decides whether the turn is small talk, a job for a single agent, or a task that needs a plan.
| Control | What it does |
|---|---|
| Model for quick decisions | The model that makes that check. It is also used for yes/no checks on conditional steps and for direct replies. |
A small, fast model is the right choice here. This model runs on every turn, including the ones that turn out to be a greeting.
3. Planning
When a turn needs several agents, this model reads every member’s skills and writes the plan.
| Control | What it does | Default |
|---|---|---|
| Planning model | Writes the plan. | Project default |
| Largest plan | The most steps a plan may contain. A bigger plan is rejected, not trimmed. | 10 steps |
| Run at the same time | How many independent steps may run together. Higher finishes sooner and spends more at once. | 8 steps |
Planning model is the setting that most changes plan quality. A stronger model is worth it when you have many members with overlapping skills, because telling them apart is the hard part of the job. Leave Model for quick decisions small regardless.
6. The final answer
Optional. When you set a prompt here, a last step composes every step’s output into one reply.
Leave it empty when your last agent already writes a good reply — the outputs are then joined directly, which costs nothing and never fails. That is also the fallback if composition fails, so a plan never dies on its last step.
A composition prompt might read:
Combine the findings below into a single answer for the user. Cite which agent produced each part.
Turn budget
Below the groups is a bar showing the worst case for one turn against the limit you have set.
| Control | What it does | Default |
|---|---|---|
| Total agent runs per turn | The hard stop for the whole turn. Reaching it finishes the turn with what it has, and says so. | 40 runs |
The number beside the bar is what a turn could cost at your current settings, counting every retry and re-plan plus the deciding and planning calls. If that estimate goes over your limit, the bar turns amber and the panel tells you: raise the budget, or lower one of the limits feeding it.
The estimate is a worst case, not a forecast. Most turns use a fraction of it. It exists so a combination of generous limits cannot surprise you with a turn that stops halfway.
Advanced
Collapsed by default, and labelled safety rails. You rarely need these.
| Control | What it does | Default |
|---|---|---|
| Longest chain of dependent steps | How deep the plan’s dependencies may go. Depth is what makes a turn slow, because each level runs in sequence. | 5 |
| When nobody is available to approve | What a member’s approval request does on an unattended turn. See Loops, failures & approvals. | Wait for approval |
| Temperature — quick decisions | Sampling temperature for the deciding model. | 0.1 |
| Temperature — planning | Sampling temperature for the planning model. | 0.1 |
Both temperatures are low on purpose. Planning is a classification job, and a creative planner produces plans you cannot predict or test.
What to change first
- Nothing. The defaults run a sensible turn. Add members and test before tuning.
- Planning model, if plans pick the wrong agents.
- Largest plan, if you see plans rejected for being too big.
- Run at the same time, if turns are slower than you want and your members are independent.
Save your changes
Click Save in the header. The preview runs the saved configuration, so save before you test a change.
Common issues
- A plan was rejected for being too large — Raise Largest plan, or split the goal across turns.
- Turns are slow — Check Longest chain of dependent steps. A deep plan runs level by level, so depth costs more time than width.
- The turn budget bar is amber — Your worst case is above Total agent runs per turn. Raise it, or lower a limit above it.
- Plans pick the wrong agents — This is almost always skills, not settings. See Your team.