# Workstream Automations

Run recurring work for a workstream on a schedule, bring each run's results back to the orchestrator or an agent, and manage those automations from the Automations tab.

An automation runs recurring work for a workstream, such as a daily summary or a weekly check, and brings each run's results back into the workstream. Workstream automations are regular [Automations](/automations/overview). This page covers how they work inside a workstream.

## Create an automation

Ask the orchestrator in plain words, for example:

```text
Every weekday at 9am UTC, summarize the open TODO comments in the repo
and post the summary here.
```

The orchestrator creates the automation or has an agent create it. When it notices work that repeats, it may also propose an automation and create it once you agree. Agents can create automations too.

## Where runs go and where they run

Runs are usually delivered to the session that created the automation, so the orchestrator or that agent picks up each run's results in the workstream.

A delivered run happens on the machine of the session it's delivered to:

- **A cloud computer**, such as the workstream's computer from an environment or a Factory-managed Droid Computer: runs keep happening after you close your laptop.
- **A computer connected through Remote Control**: scheduled runs start only while that computer is on and online.
- **This computer (Local)**: the desktop app must be running for scheduled runs to start.

## The Automations tab

To see a workstream's automations, select **+** in the right pane and choose **Automations**. The tab lists every automation that delivers to the orchestrator or one of its agents:

{/* sweep-allow: term-bullets */}

- **Title**: the automation's name, with a dot that shows its status, such as active or paused.
- **Type**: what starts a run, such as **Scheduled**, **Slack**, **GitHub**, or **Webhook**.
- **Runs on**: the computer or environment where runs happen.

Use **Search automations** to find one by name, and **Filter by status** to show only active or paused automations.

![Automations tab with one scheduled automation, showing its title, its type, and the machine it runs on](/docs-assets/images/workstreams/automations-tab.webp)

## Manage an automation

Use the row menu to pause, resume, or delete an automation.

Click an automation to open its details in the tab:

{/* sweep-allow: term-bullets */}

- **Overview**: its schedule, model, visibility, owner, where it runs, its last run, its success rate over the last 7 days, and its prompt, plus **Events**, a list of recent runs with a link to each run's session.
- **Dashboard**: how many runs there were, the success rate, failed runs, average duration, and a chart of runs per day.

From the details, you can:

- Select **Edit** to change its name, description, and schedule.
- Select **Run now** to start a run right away.
- Pause, resume, or delete it.
- Select **Open in Automations** to open its full page.

![An automation's details in the Automations tab: its schedule, configuration, last run, success rate, and a successful run under Events](/docs-assets/images/workstreams/automation-details.webp)

<RelatedLinks>
  <RelatedLink href='/automations/overview' title='Automations'>
    Triggers, templates, and guided setups for every automation.
  </RelatedLink>
  <RelatedLink href='/automations/custom#create-automations-from-a-droid-session' title='Create automations from a Droid session'>
    The tools Droid uses to create and manage automations.
  </RelatedLink>
</RelatedLinks>
