Skip to content
phonebase console

Runs

A run is one attempt at one goal on one device. It is the unit worth sharing: a link to a run answers what was asked, what happened, and every action taken along the way. The control plane holds all three — the thing that looks at the screen and decides what to do next is a worker you supply.

Data source
Fixture control— not product UI. Switches which state this screen is rendering.

Every state a run can be in at once: both meanings of Queued, a run in flight, a takeover waiting on a person, and each of the five failure reasons. Two of these runs took different roads to the same missed deadline and are deliberately indistinguishable here — a stored failed run cannot tell them apart, and only their detail differs.

Runs

One row per agent run, newest first. A run is one attempt at one goal on one device.

A run does not run itself. The control plane holds the goal, the budget and the receipts; the thing that looks at the screen and decides what to do is a worker you supply. A run with no worker connected will sit at Queued until its deadline — that is the most common way a first run ends, and it is not a timeout.