Orchestrator

Orchestrator empowers Sypha to manage complex, multi-faceted projects by decomposing them into smaller, atomic subtasks. Think of it as a lead engineer delegating specific modules to specialized sub-agents, each operating in an environment tuned for that specific duty (e.g., architect, build, or debug).

Coming Soon !!!

Why Orchestrate?

• Mastering Complexity: Break down overwhelming requests (e.g., "Build a full authentication system") into focused milestones (e.g., "Design DB schema," "Implement JWT logic," "Write UI tests").
• Specialized Execution: Automatically assign each sub-milestone to the mode best equipped for it, ensuring the most accurate tools are utilised for every phase.
• Context Hygiene: Each subtask operates in total isolation with its own dedicated conversation history. This prevents the primary "orchestrator" thread from becoming saturated with low-level execution details, maintaining a clear "big picture" overview.
• Linear Synchronization: The output of a completed subtask can be intelligently fed into the initiation of the next, creating a cohesive construction cycle.

The Operational Cycle

1. Analysis: Sypha analyzes your high-level request and authorizes a sequence of subtasks.
2. Delegation: The parent task is suspended, and a new sub-agent initiates the first milestone in the designated mode.
3. Execution: The sub-agent works until the milestone is reached.
4. Resumption: Control returns to the parent Orchestrator, which receives a comprehensive Summary of the work performed. It uses this intelligence to initiate the next phase.

Strategic Considerations

• Manual Authorization: By default, Sypha requests your approval before initiating or finalizing any subtask. This can be streamlined via Auto-Approval Settings.
• Intelligent Information Handoff: Because subtasks are isolated, information must be passed explicitly:
  • Inbound: Detailed instructions are sent from the parent to the sub-agent at initiation.
  • Outbound: Only the summarized "result" returns to the parent. Detailed chat history from the sub-agent is not inherited by the parent.
• Visual Hierarchy: The Sypha interface clearly displays the relationship between parent and child tasks, allowing you to monitor the entire assembly line.

[!TIP] Maintain Atomic Focus: If a conversation begins to drift or grows too complex, manually trigger Orchestrator to clean up the workspace and refocus the agent on a specific sub-goal.

---

Learn more about how Sypha manages these transitions in our Tool Use Overview.