# Work on a run together

At the end, you know who can open a run, what they can do in it, and what is heard in Slack.

## At a glance

**Time:** 5 minutes to read, 10 with a teammate.

**What you need:**

- Your team's runner, with you and a teammate in the org: [Set it up for your team](team.md)

## How it works

**Everyone opens the same workbench.** On a runner, every member of the org opens it from the portal's **Devices → Open**, or from **Open in workbench** in a Slack post. The portal signs them in once; the sign-in lasts thirty days from its last use.

**A run is the same page for everyone.** Every word each step was sent, every word it said back, every check and every decision. Nobody sees a different version.

**Anyone can steer it.** Any member can type in the box to the step at work or the one waiting, answer a decision, raise a ceiling in Setup, or open **Needs you**. Signing in engines, adding workspaces, and setting up GitHub and Slack stay with an owner or admin.

**The record names who.** The run records the member who started it, and each reply, decision and change records the member who made it. The portal's audit names the member too, with metadata only.

**On a laptop there is one person.** The workbench there is yours alone.

**In Slack, the thread's starter is heard.** The thread is the record for the channel: the card, each reply, each question and the finish. Only the person who started the thread is heard in it. A teammate who should decide opens **Open in workbench** and answers there.

**A gate can name a teammate.** In the builder, a gate's **Who decides** takes an email. When that gate opens, the Slack thread mentions the person and their press decides it; the workbench's card and Needs you say who it waits for, and anyone there may still answer.

## Try it

1. **Start a run with an Interactive step** from the workbench, and copy its address.

2. **Open the address in a second browser, or send it to a teammate**, who opens the runner from the portal first.

   You should see: the same conversation in both, every message and every sent bubble.

3. **Reply to the waiting step from each browser, one after the other.**

   You should see: both replies in the conversation, `You → <step> · reply`, and the step answering each in the same session.

## Check

On the box, in the `loopgate` folder, read the run's record (its id is in its workbench address):

```sh
docker compose exec runner grep -o '"startedBy":"[^"]*"\|"userId":"[^"]*"' /data/runs/<run>/events.jsonl
```

You should see: the member who started the run, then the member behind each reply, decision and change.

## Next

The same run from Slack: [Slack as the workbench](slack-workbench.md).