Orchestrator
The Orchestrator page is the dashboard surface for the control-plane agent that routes and supervises work.
The orchestrator is not just another role. It is the part of the system that decides what should happen next, which is why it gets a dedicated surface instead of being buried under generic role settings.
What Lives Here
Section titled “What Lives Here”- orchestrator prompt baseline
- model-routing posture for orchestrator work
- pool posture and related execution defaults
Why It Matters
Section titled “Why It Matters”Use this page when you need to tune how the orchestrator plans, routes, or supervises specialist work. The effects tend to show up across the whole product, not just in one role.
A small change here can alter how aggressively the system decomposes work, revisits blocked situations, or delegates tasks to specialists.
Because the orchestrator owns planning and recovery decisions, weak
model choices show up here quickly. For the best current balance of
quality and end-to-end speed, we recommend gpt-5.4 with at least
low reasoning, and usually medium, rather than a low-capability or
non-reasoning model.
How It Connects To The Rest Of The System
Section titled “How It Connects To The Rest Of The System”The orchestrator sits between authored process and specialist execution:
- Playbooks And Authoring defines the workflow intent and process the orchestrator is trying to drive to closure
- Workflows and Workflow Detail show the orchestrator’s downstream effects as activations, tasks, board movement, and intervention moments
- Specialists, Skills, And Models defines the specialist pool the orchestrator can route into
- Models and Agentic Settings shape how that orchestration behaves under load
This page answers “how should the control-plane brain behave?” The workflow surfaces answer “what did it decide on real work?”