Orchestrator
The Orchestrator enables multi-agent projects where a boss agent delegates tasks to worker agents.Concepts
Creating a project
- Go to Orchestrator in the sidebar
- Click New Project
- Fill in:
- Title — project name
- Goal — what the project should accomplish
- Boss agent — the agent that leads
- Workers — add agents with specialties
Agent specialties
Each agent on a project team has a specialty that determines how they’re prompted and which model they use. The orchestrator supports two sets of specialties depending on context:Project sub-agents (create_sub_agent)
When the boss agent dynamically creates sub-agents during a project run:
Standalone agents (create_agent)
When creating agents via the create_agent tool or the Agents view:
:::tip Custom system prompts
Every agent — regardless of specialty — can have a custom system prompt set at creation time via the
system_prompt parameter. This gives you full control over the agent’s behavior and personality beyond the specialty label. The boss agent can use create_sub_agent with a detailed system_prompt to create highly tailored workers on the fly.
:::
Specialty models can be configured in Settings → Engine under Model Routing. For example, setting coder to gemini-2.5-pro routes all coding tasks to that model.
How it works
Boss tools
Worker tools
Workers have access to all standard safe tools plus:report_progress— send status updates back to the boss- Statuses:
working,done,error,blocked
- Statuses:
Project statuses
Message bus
The project detail view shows a real-time message bus (polled every 3s):Model routing
Configure which models handle what in Settings → Engine:
Resolution priority: agent_models > specialty_models > role-based > fallback
Cheap model & auto-tier
The cheap model setting lets you reduce costs by routing simple tasks to a smaller, faster LLM while keeping the full model for complex work. Whenauto_tier is enabled, every incoming message is classified by a complexity heuristic before model selection:
The classifier looks for signals like code keywords (
implement, refactor, debug), reasoning phrases (analyze, compare, step by step), multi-step patterns (and then, first,, numbered lists), and message length (>1500 chars → complex).
Example model routing config
auto_tier / cheap_model mechanism applies to regular chat sessions. Within orchestrator projects, model selection uses the boss_model → worker_model → specialty_models → agent_models routing chain instead.
:::
Execution limits
Orchestrator projects are bounded by the engine’s global execution limits:
The boss agent loop exits when:
project_completeis calledmax_tool_roundsis exceeded- An unrecoverable error occurs
report_progressis called with statusdonemax_tool_roundsis exceeded- An error occurs

