# Steer a run as a team

Returns: One run, many hands. Starts: from the console.

A teammate starts a run; everyone in the org can read it as it works, and its starter or an org admin steers it with follow-ups or by taking control of its browser.

## Best for

- Reviewing a teammate's run while it works, without a screen share
- Teams where one person starts work and an admin can step in

## Uses

- A Project
- Teammates in your org

## The request

`POST /o/{org}/sessions`

```json
{
  "harness": "codex",
  "input": "Reproduce the checkout bug from ENG-51 in the browser and fix it.",
  "resources": [
    {
      "url": "https://github.com/acme/web"
    }
  ]
}
```

## While it works

Live stream events (`GET /o/{org}/sessions/{session}/events`):

- `tool_use`: browser · open localhost:3000/checkout
- `thinking`: The coupon field clears on blur.
- `message`: Found it in CouponInput.tsx.

## What comes back

- `status`: running
- `turns_count`: 3, two of them follow-ups

## Steps

1. **Bring the team in.** Teammates join your org with its invite code. Everyone in the org sees its Projects and their runs, with who started each.
2. **Read it as it works.** Any org member opens the run and reads its transcript as the agent works.
3. **Steer it.** The run's starter or an org admin sends follow-ups (the console queues one sent mid-turn) and can take control of its browser on a five-minute lease that one person holds at a time.

Field names are the API's; the values are an example.