Agent sessions
Watch a running agent, answer its permission and input requests, review its diff, and control the run.
After you dispatch a run the agent works inside a devbox, and you watch and steer it from the agent session console. Open Agent sessions from the navigation, pick a session from the list, and its console opens on the right. The console has five tabs: Transcript, Terminal, Runtime, Review, and Session.
Watch the transcript
The Transcript tab streams the agent's messages and tool calls as they happen. When you open a session, retained history replays before the live stream continues. Transcript and event history expires after 90 days. If your connection drops, the transcript reconnects on its own and resumes from where it left off without duplicating retained events.
The other tabs read from the same live stream: Terminal shows command output, Runtime shows event, tool, and changed-file counts, and Session shows the model, the task prompt, and what the session is bound to.
Answer the agent
When the agent needs a decision, a card appears over the transcript and stays until you respond.
- Permission requests — the agent asks to run a command or touch a path. Choose Allow once, Allow session to approve every later request in this session, or Decline. A reason is optional.
- Questions — the agent asks you to choose. Pick one of the offered options or type your own answer, then Submit answer.
The composer at the bottom is always open: send a follow-up message any time to steer the agent, add context, or ask for a status update, then Send message.
Approvals, answers, and messages reach the agent only while the session is Running with a live runner. If the runner has dropped, the action fails until a runner reconnects. See Troubleshooting.
Review the changes
The Review tab shows every file the agent has changed, in unified or split diff.
- Select lines in a diff and choose Add note to attach a review comment. Edit or remove a note from its menu.
- Submit review opens Finish your review, where you write a summary, see your pending comments, and send them to the agent — or Discard review to clear them.
When the run reports a pull request, its run detail shows a Pull request link to the repository provider. The Pull requests screen combines open provider results with pull requests reported by runs during the last 90 days.
Control the session
The header shows the session title, its status (Starting, Running, Completed, Failed, Stopped, Cancelled, or Archived), the model, and the devbox. A session still waiting for a runner shows as Starting — why it waits is Dispatching runs. Three actions sit beside the status, each available only in the right state:
| Action | Available when | What it does |
|---|---|---|
| Rerun | The session has finished and is not archived | Re-queues it with a fresh attempt; a runner picks it up again |
| Force stop | The session is starting or running | Stops the session; a runner that has claimed it is asked to halt the container |
| Archive | The session is not already archived — stop an active one first | Sets its status to Archived; it stays in the list and can no longer be rerun |
Every write here — approvals, answers, follow-up messages, reviews, Rerun, Force stop, and Archive — requires an organization owner or admin role, enforced on every request. Members open the console read-only: the session controls and the composer are disabled, and any write a member submits is refused. See Security.
Next: Managing credentials — the provider credentials runs depend on, in depth.