From the consoleNeeds a repository

Steer a run as a team

One run, many hands

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.

View .md

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

From the console

POST /o/{org}/sessions

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

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

Watch it work, then read what comes back

GET /o/{org}/sessions/{session}/events

event: tool_usebrowser · open localhost:3000/checkout

event: thinkingThe coupon field clears on blur.

event: messageFound it in CouponInput.tsx.

Fig. The live stream while it works. Event names are the stream's.

GET /o/{org}/sessions/{session}

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

Fig. The session when it ends. Field names are the API's.

Steps

01
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.
02
Read it as it works
Any org member opens the run and reads its transcript as the agent works.
03
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.