# Autopilot and how much Andon does

Andon can build, review and merge a team's work on its own, or only do what you start. **How much Andon does** sets
that for the workspace and for each team. **Autopilot** is the part that starts work: with it on, every card you move
into a team's Ready builds by itself.

## Pick how much Andon does

There are three levels:

| Level | Runs cards | Reviews pull requests | Merges | Moves cards to Done | Autopilot |
|---|---|---|---|---|---|
| **Manual** | no: cards are done by hand | no | no | no | off |
| **Assist** | the cards you start | yes | you merge | when the pull request merges | off |
| **Ship** | every Ready card | yes | yes, unless it touches a protected path | yes | on |

To set it for every team:

1. Open **Settings → Automation**.
2. Under **How much Andon does**, pick **Manual**, **Assist** or **Ship**.

The line under the choice says what the level does. Every team follows it unless it sets its own.

To set it for one team:

1. Open **Settings → Teams** and pick the team.
2. Under **Overrides**, pick a level in **How much Andon does**. Leave it on the workspace's to follow Automation.

A new team with a repository starts on **Ship**; one without starts on **Assist**.

The level is a shortcut for a handful of switches: cards done by hand, Autopilot, auto review, auto merge, and Done
on merge. If a team's switches don't match one level exactly, Andon shows the closest and names the switches that
differ, with a link to set them to that level. The review rounds, CI fix attempts and merge method are separate: they
never move a team off its level. See [Pull requests: review and merge](https://andon-docs.pages.dev/guide/review-and-merge.md).

## Turn Autopilot on for a team

Any of these, as an owner or admin:

- On the board, with **Swimlanes** set to **By team**, use the **Autopilot** switch in the team's lane header.
- Click **Autopilot** in the board's toolbar and pick **On** beside the team.
- On the team's page, use the switch under **Autopilot**.
- When a team has Ready cards and Autopilot is off, the board offers *Let Autopilot build …*: click **Turn on
  Autopilot**.
- Search Settings for **Autopilot** and pick the team.

Picking **Ship** for a team also turns Autopilot on. **Manual** and **Assist** turn it off.

## How Autopilot builds Ready cards

Ready is the queue. Moving a card into Ready means "build this"; there is no plan to approve. With Autopilot on,
Andon:

1. **Places the new cards.** Cards that enter Ready within 30 seconds of each other are looked at together. Related
   cards go into one pull request group, and a card that builds on another is marked as waiting for it. These links
   show as *placed by Claude*: remove one in one click, or keep it.
2. **Starts the next one.** In Ready order, it starts the next card or group whose dependencies are done, while the
   team has a free slot and a machine with the repository is online and takes queued work.
3. **Reviews and merges** the pull request, as the team's level says.

Each Ready card has a status line that says what it waits for:

| Status line | Means |
|---|---|
| *Next up* | It starts as soon as Andon checks again |
| *Being placed with 3 other new cards*, *Claude is placing it* | Placement hasn't answered yet |
| *In "Checkout fixes" with WEB-3* | It is part of a group, which builds as one pull request |
| *Own PR: …* | Placement left it on its own, and says why |
| *Waiting for WEB-7 to merge* | A card it depends on isn't merged |
| *Waiting for a slot: 2 of 2 PRs building* | The team is building as many pull requests as it may |
| *No machine has the web repo online*, *No machine takes queued work* | No machine can take it |
| *Waiting for a machine: 4 of 4 runs going* | Every machine that could is busy |
| *Waiting: project held* | Its project is held (below) |
| *Autopilot is paused for Web*, *All autopilots are paused* | Nothing new starts |
| *Done by hand: Autopilot leaves it*, *A sub-task: it builds with its parent*, *Has sub-tasks: Autopilot leaves it to you*, *Pinned to a machine: Autopilot leaves it to you* | Autopilot doesn't start this card |

A card whose last run ended without finishing (its session was stopped or lost, or the run failed) picks up where it
stopped when it starts again: it continues that session in the card's worktree, or starts in that worktree when there
is no session to continue. When that worktree is still there but can't be used (the card is pinned to another
machine now), the run starts in a new one and its prompt names the earlier worktree, so the work left there isn't
lost. A card whose worktree was removed starts in a new one as before.

The lane header sums up the team's Ready cards. Click **Autopilot** in the toolbar, then **Re-check Ready**, to have
Andon look again at once.

A card is placed again when it re-enters Ready, when its title or notes change, or when you pick **Re-place** in its
⋯ menu.

## Autopilot's team settings

Search Settings for one of these and pick the team:

| Setting | What it does |
|---|---|
| **Autopilot** | **On** or **Off** for this team |
| **Group related cards** | On: related Ready cards ship in one pull request. Off: every card is its own |
| **PRs building at once** | How many of the team's pull requests build at the same time |
| **Max cards per PR** | Under **Advanced**: the most cards in one pull request, 1 to 12 |

A team that leaves **PRs building at once** blank follows the workspace's: **Pull requests building at once** on
**Settings → Automation** under **Guard rails**, 1 to 100. That row names the teams that set their own. Left blank there
too, a team builds 2 pull requests at once, and runs started by hand aren't capped. A number, the team's or the
workspace's, also caps the team's runs at a time, sub-teams included. A run past the cap waits, its card saying
"waiting for a slot in andon (10 at a time)" with the team's name and cap; **Change** beside it opens that team's **PRs
building at once**. A team that leaves the other settings blank groups related cards and puts no cap on a pull
request's cards. A sub-team doesn't take its parent's. **Group related cards into one pull request**, on the same page,
lists each team's value, with a link to change it on Teams.

## Hold work back

Nothing else gates Autopilot. To keep work from starting:

| To hold | Do this |
|---|---|
| one card | Leave it out of Ready, or set **Done by** to **Me** |
| one project | Open the project's page and click **Hold this project**. Its Ready cards and groups wait; runs already going finish, and a card you start by hand still runs. **Release this project** starts them again in Ready order |
| one team | Click **Pause** in the team's lane header, or **Pause this team** beside its name in Settings → Teams. **Resume** starts it again |
| every team | Click **Autopilot** in the board's toolbar and turn on **Pause all autopilots**. What is building goes on |

A held project is marked in the sidebar, and its page says *Held · nothing new starts*.

## Grouping by hand wins

A group you made, or a group you changed, is yours: Autopilot never regroups it. A card you take out of a group isn't
put back. A new group you make waits 15 seconds before Autopilot may start it, so Undo still finds it. See
[Teams, projects and PR groups](https://andon-docs.pages.dev/guide/teams-projects-and-pr-groups.md#pr-groups).
