> For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt.

# Orchestrator

Orchestrator lets Sero's AI agents work on a task without you directing every
step. You describe the result you want, review how Sero plans to do the work,
and decide when it can start.

Open Orchestrator from the app bar, then choose **Workflows** or **Rooms**. A
third mode, **[Goals](/guide/goals.md)**, starts in the chat session itself with
`/goal`, and Orchestrator manages the ones you leave running.

## Choose a Workflow, Room or Goal

- Use a **[Workflow](/guide/workflows.md)** when Sero can plan the work before it
  starts. For example, a Workflow can collect the week's project notes, write a
  summary, ask you to review it, and save the approved version. You can run a
  Workflow once, on a schedule, or after an event.

- Use a **[Room](/guide/rooms.md)** when several agents need to work together. Sero
  creates a temporary team, gives each member a role, and lets them share their
  findings. For example, one member can review the cost of a project, another
  can review the schedule, and a third can check the risks. The team then
  combines its findings into one report.

- Use a **[Goal](/guide/goals.md)** when you want the session you are already in to
  keep working until a result is reached. Sero plans nothing first. You say what
  must be true at the end, and the session keeps going until it is.

- Use **[Architect](/guide/architect.md)** when you want Sero to build and
  maintain a product from an idea. You give it a request and a start cap. It
  plans the work as it learns, does small milestones itself and dispatches the
  rest to Workflows and Rooms, checks the result, then releases and maintains
  it. You answer the decisions that need your input.

Choose a Workflow for planned steps, a Room for a team, a Goal for ongoing work
in the current chat, or Architect for a product that Sero will build and
maintain.

|              | Workflow                 | Room                                                | Goal                             | Architect                                                          |
| ------------ | ------------------------ | --------------------------------------------------- | -------------------------------- | ------------------------------------------------------------------ |
| Sero creates | A plan of steps          | A team of agents                                    | Nothing to review first          | A plan of milestones inside your start cap                         |
| Work happens | Step by step             | Members work and share findings                     | In your chat session             | Milestone by milestone, by the Architect or in Workflows and Rooms |
| Use it for   | A task with clear stages | A task that needs different roles or points of view | One result with an unknown route | A product that Sero builds, releases and maintains from an idea    |

You do not need a Workflow before you start a Room or a Goal. They are
independent.

## What stays under your control

Sero shows you what it proposes before work starts. For a Workflow, you review
the steps. For a Room, you review the team and each member's role.

You also review:

- which files and tools the agents can use;
- how long they can work and how much they can spend;
- where Sero will put the result.

Your workspace is the project or folder that you opened in Sero. Sero asks for
approval before it sends a result outside that workspace.

Access settings control the tools available to an agent. They are not a
sandbox. An agent with shell, or command-line, access can run any command that
your account can run. Use Orchestrator only in a project that you permit it to
change.

Orchestrator pauses the work when it needs:

- an answer to a question;
- your approval for an action;
- more time or a higher cost limit;
- help after something failed.

A Room has a limit on its working time. Only the time its members work counts:
time while Sero is closed, or while the Room waits for you, does not. When a
Room uses its time, it stops with its work kept. Select **Add time…**, enter a
larger total and select **Approve and resume**. The same Room continues, and its
spend cap does not change.

Each row and page shows what the work does now: the step or the member, the
tool it runs, or "waiting for the model" with the time when a model request is
slow. If Sero cannot confirm that the work is live in this session, the row says
"Last known".

You can close Orchestrator while the work continues. **Home** shows questions
and approvals that need your attention. Sero notifies you when the work finishes
or cannot continue.

## Start here

- [Create and run a Workflow](/guide/workflows.md): the tutorial.
- [Manage Workflows](/guide/workflows-advanced.md): schedules, recovery,
  Library and Catalog.
- [Create and run a Room](/guide/rooms.md): the tutorial.
- [Manage a Room](/guide/rooms-advanced.md): claims, limits, and the changes a
  team can make while it works.
- [Architect](/guide/architect.md): a product from idea through maintenance.

For exact tool names, commands, and compatibility terms, see the
[Orchestrator reference](/reference/orchestrator.md), the
[Workflows reference](/reference/workflows.md), and the
[Rooms reference](/reference/rooms.md).
