Run

Watching a run

While a run works, the chat shows what Auprimus is thinking and the DAG tab shows every step, with the run's time, tokens and cost live.

In the chat

Every thought, decision and response appears as it happens, with its tokens, cost and time. This is where Auprimus asks for confirmation when your guardrails require it.

In the DAG tab

The workflow appears as a graph of steps, each showing its status as it waits, runs, succeeds or fails. The header shows:

ShownWhat it tells you
Run timeCounts up from when the steps start running, and stops when the run ends. It survives a page refresh.
Input and output tokensTotals for this workflow, updated while it runs.
CostThe total cost of this workflow so far.

Use Layout (Stacked, Dagre LR, Dagre TB) and Edges (Smooth, Bezier, Straight) to arrange the graph, and turn the MiniMap and Grid on or off.

Alerts and retention for the project

Guardrails, under the message box, sets for the whole project which alerts to raise (a step failed, a re-plan, a scheduled run failed, a confirmation waiting, a long run or step) and how long run files are kept before they are deleted.

NoteSelect any step to open its console: logs, traces, metrics, lineage, cost and the code it ran. See The step console.
Something wrong or missing? Write to [email protected] about “Watching a run”.Updated 11 Oct 2026