# Needs you

Needs you is the list of everything waiting for a person: a question from a run, a finished turn, outputs to approve,
a failure, a pull request that needs a hand. Work through it and the agents keep going. The count beside **Needs
you** in the sidebar is how many items wait for you.

## Work through it

1. Click **Needs you** in the sidebar. On a phone it is the first tab.
2. Pick an item. Its card opens with a bar on top that says what the item asks and how long it has waited.
3. Answer it: the bar's buttons, or the card's own **Needs you** box under it, do what the item asks. For a question
   from the run, the bar says *Answer it below*. A run that ended blocked on a decision asks it in the run's report on
   the card, with its choices and **Send answer**.
4. The item leaves the list once it is answered. Pick the next one, or press `.` on the board to jump to the next card
   that needs you.

On a desktop window 1280 px wide or more, the list stays on the left and the card opens on the right. On a narrower
window or an iPad the card opens as a panel over the list.

On a phone, each item carries its own buttons on the list, such as a reply box for a finished turn, **Retry** or
**Merge now**. Its ⋯ menu holds the item's own other actions, then **Snooze for an hour**, **Snooze until tomorrow** and
**Dismiss**. Answer it there,
or tap it to open the card. A terminal wider than the phone is scaled to the screen's width, so whole lines show; turn
off **Fit width** for actual size and scroll sideways.

An item with no card, such as a machine offline or an import rule failing, has its buttons in the list row itself.

## What the list holds

Items are grouped by what they ask, in the order you'd handle them. The chips at the top filter the list to one group.

| Group | What's in it |
|---|---|
| **Decisions** | A run is blocked until you answer: **Needs input**, **Question**, **Blocked**, **Out of credits**, **Interrupted**, **Interrupted runs** |
| **Your turn** | **Waiting for you**: a turn finished; reply, or mark the card done |
| **To review** | **Outputs ready**, **Plan to review**, **Ready to merge**, **Looks finished?** |
| **Failures** | **Run failed**, **Step failed**, **Pipeline stopped**, **PR closed** |
| **Pull requests and dates** | **PR needs attention**, cards that can't run yet, and **Due**: a card with a due date that isn't in Working, Done or the Backlog |
| **System** | **Machine offline**, **Stuck in queue**, **Linear import failing**, **Overdue** (a card in Working or the Backlog past its date) |

A due date counts as soon as the card has one, whether the date is next month or last week: the row says when
(*Due tomorrow*, *Overdue: due Nov 12*), and the soonest comes first. Move the card to Working, or snooze or dismiss
the item, to quiet it. A dismissed due date comes back once, when the card falls overdue. A card in Working or the
Backlog says nothing about its date until the date passes, and then only in the System group.

A card shows once, as its most pressing item. *+2* on a row, and *Also: …* on the card, name its other items. Each
comes up on its own once the first is dealt with.

The headline counts what waits for a person and says how old the oldest is. System items don't count: they show in
their own quiet group and never light the [Dashboard](https://andon-docs.pages.dev/guide/dashboard-and-phone.md) lamp.

## An interrupted run

When a run's session dies mid-work, the run is **Interrupted**, not finished. That happens when its terminal is
killed, the agent's tmux server goes down, or Claude exits while it is working. The card stays where it was (a study
doesn't move on to Review) and says **Interrupted** in amber. Its item reads *Interrupted: Resume or Stop*:

- **Resume** carries the run on in the same session and the same worktree, in one click. The session is sent a note
  that says when it was interrupted, which command was running, and the worktree's `git status`, then tells it to
  carry on with the card. You don't have to type anything.
- **Stop** leaves the card as it is and takes the item off the list.

When several runs on one machine are interrupted within a few minutes, you get one item, **Interrupted runs**, that
says how many ran on which machine and when (*3 runs on Studio Mac were interrupted at 15:31*). It lists their cards,
and **Resume all** resumes each one in its own worktree. The machine's row in **Settings → Machines** shows the same
list with **Resume all**.

A run that had already opened its pull request ends as before and isn't listed. A machine that rebooted or went
offline still tries to resume its runs by itself when it is back. Only a run it can't resume becomes **Interrupted**.

## Snooze or dismiss an item

Each item's bar or row has both:

- **Snooze** puts it away **For an hour** or **Until tomorrow morning**.
- **Dismiss** takes it off the list for good. It comes back only as a new item, such as a pull request with a new
  problem.

Snoozing is yours alone: it doesn't hide the item from anyone else.

## Needs you everywhere

If you use more than one Andon instance, for example your own and a team's, one of them can show what needs you on
all of them. That one is your **home instance**.

Connecting instances is **experimental** and off unless each instance's server turns it on: its admin sets
[`ANDON_INSTANCE_CONNECT`](https://andon-docs.pages.dev/reference/env.md) to `on`. While it is off, **Settings → Instances** says so and offers
no **Connect an instance**, the rail and **Needs you everywhere** don't show, and connections made before stop working
until it is on again. The
[desktop app](https://andon-docs.pages.dev/guide/desktop-app.md) switches between instances without it.

### Set it up

1. On the instance you want as home, open `/settings/instances`, or search Settings for **This is my home
   instance**.
2. Turn on **This is my home instance**.
3. Under **Connected instances**, type the other instance's address and click **Connect an instance**.
4. The other instance asks you to say yes, where you are already signed in. Say yes.
5. Repeat for each instance.

Once an instance is connected, **Instances** shows as a tab on **Settings → Machines**, and a rail of your instances
appears at the left edge of the window.

### Use it

Click the alarm-clock tile at the top of the rail, or open `/everywhere`. **Needs you everywhere** lists what needs
you on every connected instance, most pressing first, in the same groups as Needs you. Each row names its instance.

- Act on a row in place: its buttons run on its own instance, and a finished turn has a reply box right in the row.
- Click a row's title to open its card. A card on another instance opens there, in a new tab.
- A tile with a count on the rail goes to that instance in this tab.

An instance that doesn't answer is named under the list with its error. To stop a home instance seeing an instance,
open **Settings → Machines → Instances** on that instance and **Revoke** it under **Connected to this instance**.

A connection also ends when your password is reset, when you change it (a change signs your other sessions out), and when your
account there is banned or deleted. Connect the instance again from home afterwards.

The rail and Needs you everywhere work in a browser on an instance served by the Andon server. The
[desktop app](https://andon-docs.pages.dev/guide/desktop-app.md) has its own way to switch between instances.
