packages/kilo-docs/pages/code-with-ai/agents/orchestrator-mode.md
{% callout type="warning" title="Deprecated — scheduled for removal" %} Orchestrator mode is deprecated and will be removed in a future release. In the VSCode extension and CLI, agents with full tool access (Code, Plan, Debug) can now delegate to subagents automatically. You no longer need a dedicated orchestrator — just pick the agent for your task and it will coordinate subagents when helpful. (Read-only agents like Ask do not support delegation.) {% /callout %}
Previously, orchestrator mode was the only way to break complex tasks into subtasks. You had to explicitly switch to orchestrator mode, which would then delegate work to other modes like Code or Architect.
Now, subagent support is built into agents that have full tool access (Code, Plan, Debug). When one of these agents encounters a task that would benefit from delegation — like exploring a codebase, running a parallel search, or handling a subtask in isolation — it can launch a subagent directly using the task tool. There's no need to switch agents first.
task tool (e.g., general for autonomous work, explore for codebase research).Agents can launch multiple subagent sessions concurrently for parallel work.
{% callout type="info" title="VSCode (Legacy)" collapsed=true %} In the legacy extension, orchestrator mode uses two dedicated tools:
new_task — Creates a subtask with context passed via the message parameter and a mode specified via mode (e.g., code, architect, debug).attempt_completion — Signals subtask completion and passes a summary back to the parent via the result parameter.{% youtube url="https://www.youtube.com/watch?v=20MmJNeOODo" caption="Orchestrator Mode in the legacy extension" /%} {% /callout %}