> ## Documentation Index
> Fetch the complete documentation index at: https://docs.twin.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Orchestrator

> The workspace-level chat that manages all your agents

The Orchestrator is the left-side chat in your workspace. It has full context on every agent, run, and schedule — and it's how you create, modify, and manage agents using natural language.

## What Is the Orchestrator?

The Orchestrator is your workspace's command center. Instead of configuring workflows step by step, you describe what you need and the Orchestrator handles everything — from creating agents to coordinating multi-agent workflows.

It knows about all agents in your workspace, their goals, their run history, and their current state. This means you can ask it to do things like:

* "Create a new agent that monitors competitor pricing"
* "Update the lead scraper to also extract LinkedIn profiles"
* "Delete the old reporting agent, I don't need it anymore"
* "Schedule the data collector to run every morning at 8am"

## How the Orchestrator Works

<Steps>
  <Step title="Describe what you need" icon="lightbulb" color="#F4D03F">
    Explain your goal in natural language. The Orchestrator analyzes your request, determines which agents are needed, and proposes a plan.

    Before anything runs, you can review and adjust the plan to make sure it matches your expectations.
  </Step>

  <Step title="Build or modify agents" icon="hammer" color="#F4D03F">
    Once the plan is approved, the Orchestrator creates or updates agents behind the scenes.

    This includes:

    * Defining the execution logic
    * Setting up navigation and decision points
    * Connecting outputs to your tools
    * Handling retries and edge cases
  </Step>

  <Step title="Clarify when needed" icon="comments" color="#F4D03F">
    If something is ambiguous, the Orchestrator asks targeted follow-up questions to avoid incorrect assumptions.

    Clarifications can happen during initial setup, while refining an agent, or when extending it with new behavior.
  </Step>

  <Step title="Test and deploy" icon="rocket" color="#F4D03F">
    After building, the Orchestrator can run test executions with real data. If something doesn't work, follow up in the chat to adjust instructions and re-run — without rebuilding from scratch.
  </Step>
</Steps>

## Proactive Suggestions

The Orchestrator doesn't just wait for instructions — it actively helps you improve your workspace.

<CardGroup cols={2}>
  <Card title="Split complex agents" icon="scissors" color="#F4D03F">
    If an agent is doing too much, the Orchestrator will suggest breaking it into focused, smaller agents that are more reliable.
  </Card>

  <Card title="Create new agents" icon="plus" color="#F4D03F">
    When it detects a workflow could benefit from a dedicated agent, it will propose creating one.
  </Card>

  <Card title="Coordinate agents" icon="diagram-project" color="#F4D03F">
    The Orchestrator can chain agents together — one agent's output becomes another's input.
  </Card>

  <Card title="Optimize workflows" icon="bolt" color="#F4D03F">
    It monitors how agents perform and suggests improvements to reduce costs or improve reliability.
  </Card>
</CardGroup>

## What You Can Do

<CardGroup cols={3}>
  <Card title="Create agents" icon="plus" color="#F4D03F">
    Turn a description like "log into a portal, download files, and store them" into a working agent.
  </Card>

  <Card title="Modify agents" icon="pen" color="#F4D03F">
    Add steps, change logic, adjust outputs, or adapt to changes — all through conversation.
  </Card>

  <Card title="Troubleshoot" icon="wrench" color="#F4D03F">
    If an agent fails, refine instructions and improve reliability directly in the chat.
  </Card>
</CardGroup>

## Why This Approach Is Different

<AccordionGroup>
  <Accordion title="Built for real-world workflows" icon="globe" color="#F4D03F">
    Traditional automation tools work best when everything has a clean API.

    The Orchestrator is designed for the opposite case: workflows that happen inside web interfaces, dashboards, and portals.
  </Accordion>

  <Accordion title="Conversation instead of configuration" icon="message" color="#F4D03F">
    There are no blocks to wire, no forms to fill, and no rigid action catalogs.

    You describe the task the way you would explain it to a teammate, and the Orchestrator handles the execution logic.
  </Accordion>

  <Accordion title="Full workspace awareness" icon="eye" color="#F4D03F">
    Unlike a single-agent chat, the Orchestrator sees your entire workspace. It can reference any agent's history, coordinate between agents, and make workspace-level decisions.
  </Accordion>
</AccordionGroup>

## Get Started

<Card title="Open the Orchestrator" icon="arrow-right" href="https://builder.twin.so/" color="#F4D03F">
  Start building your first agent now
</Card>