Skip to main content

Watch a run

Open a run from the issue's Runs list, or from Reviews once it is waiting on somebody.

Execution screenshot placeholder showing the run header, timeline and services

The header

The top of the page carries the reference, the state, how long it has been going, and five facts:

FactWhat it says
Coding agentClaude Code or Codex, or The machine's own when the machine chose
ModelThe model used, or The machine's own
MachineWhich computer it landed on
FolderWhich connected folder it is working in
SlotsHow much of that machine is in use

The states

StateWhat it means
QueuedWaiting for a machine with room.
TakenA machine has accepted it but has not started.
PreparingCopying the folder into a scratch workspace.
RunningThe coding agent is working.
Waiting on youIt stopped to ask something and cannot go on until somebody answers.
Waiting for a slotAnswered, and queued to carry on.
FinishingCommitting, pushing and opening pull requests.
Waiting for reviewDone, and waiting for somebody to accept or reject it.
ApprovedAccepted. The machine is giving the workspace back.
CompletedFinished and cleaned up.
Failed, Cancelled, InterruptedIt stopped without a result. Interrupted means the machine stopped reporting.

Answer a question

A coding agent can stop and ask. When it does, the run moves to Waiting on you and the question appears at the top of the page, above everything else.

Execution screenshot placeholder showing a blocking question with its answer options

If it offered options, each is a button. Answer this — or Say something else where options also exist — opens a box for a free-text answer. Dismiss refuses it.

Some questions carry a default the agent falls back to if nobody answers in time; the question says so. A question nobody answers in time reads Nobody answered, so the run stopped.

Answered and dismissed questions collect in a Questions section further down.

What the run is doing

Timeline — every state change, command, tool call, service event, preview and note, newest work appended live. Fifty events load with the page; Read on fetches more.

Services — anything the run started, with its port, health and why it is unhealthy if it is. Output on a service expands what it has printed.

Transcript — what the coding agent said, what it used, and what each turn cost. It shows sixty entries at a time, then Read on fetches more from the server. It is empty where the workspace keeps summaries only, or where the retention window has passed.

What changed — branches, commits, diffstat and pull requests, as they arrive. See Review a run.

Previews — anything the run has exposed. See Previews.

Stop it

Stop this run asks Stop this run? and then stops it. Use it when the run has clearly gone wrong; there is no way to resume a stopped run, only to start a new one.

Run it again appears on a run that ended without a result. It starts a fresh attempt on the same issue and takes you to it.

This run has already finished, so there is nothing to stop. means it settled while you were reading.

From the machine

norn runner executions
norn runner logs <exec>

Lists the runs that machine has taken, and what happened in one of them.