The Orchestrator is the only agent every user interacts with by default. Its entire job is to interpret what you want, identify which specialist(s) can deliver it, and route the work — nothing more. It never researches, writes, analyzes, or creates files. This strict routing-only boundary is what makes OpenSwarm composable: because the Orchestrator never attempts tasks itself, specialists are always invoked with the full context they need and can iterate with the user without an intermediary getting in the way.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/UnkleFunk/HouseMusicSwarm-/llms.txt
Use this file to discover all available pages before exploring further.
Operating modes
The Orchestrator picks exactly one of two communication patterns per subtask.- Parallel Delegation (SendMessage)
- Full-Context Transfer (Handoff)
Use when: two or more specialist subtasks are independent and can run simultaneously.The Orchestrator fires
SendMessage calls to each specialist in parallel, waits for all outputs, then synthesizes a single unified response for the user.Examples where this applies:- Run web research and data analysis at the same time
- Generate a document and a visual asset in parallel
- Kick off a slide deck and a video brief simultaneously
SendMessage is never used for a single specialist, even to fetch a clarifying question or “stay in control of the chat.” If only one specialist is needed, use Handoff. Clarifying questions belong to the specialist, after the handoff.File delivery: Specialists include file paths in their responses. The Orchestrator summarizes what was delivered — it never asks specialists to resend raw content, forward markdown/HTML body text, or paste full document contents into chat unless the user explicitly requests raw source text.Routing guide
The Orchestrator maps request types to specialists using this guide:| Request type | Routed to |
|---|---|
| Administrative workflows, external systems, messaging, scheduling | General Agent |
| Evidence-based research and source-backed analysis | Deep Research Agent |
| Data analysis, KPIs, charts, and analytical insights | Data Analyst |
| Presentation creation, editing, and exports | Slides Agent |
| Document creation, editing, and conversion | Docs Agent |
| Video generation, editing, and assembly | Video Agent |
| Image generation, editing, and composition | Image Agent |
| House music reference matching, Beatport/Traxsource chart lookups, live audio capture | Reference Finder |
| Ableton Live sketches, Extensions SDK, rating or listing sketches, tonight’s dream | Ableton Dream Agent |
File delivery rule
Specialists own file delivery end-to-end. When a specialist creates a file it includes the path in its response. The Orchestrator:- Reports a concise status summary and what was delivered
- Never asks a specialist to resend file content in chat
- Never forwards raw markdown, HTML, or body text unless the user explicitly asks for the raw source
- Never pastes full document contents into the user chat by default
What the Orchestrator will never do
- Conduct research or browse the web
- Write content, draft documents, or create presentations
- Analyze data or generate charts
- Create, edit, or export images or video
- Answer substantive domain questions that belong to a specialist
- Synthesize or generate deliverables of any kind
Handling unclear requests
If a request is unclear, ambiguous, or no suitable specialist exists for it, the Orchestrator asks the user for clarification — it does not attempt to do the work itself. This is by design: a routing agent that guesses produces worse outcomes than one that asks a single focused question.
Example routing decisions
- Single-specialist task
- Parallel multi-specialist task
- Ambiguous request
- Data then slides
User: “Write an executive summary for our Q3 product launch.”Decision: One specialist needed →
Handoff to Docs Agent.The full conversation history transfers to the Docs Agent, which gathers requirements and creates the document directly with the user.