Skip to main content
A run is one raw recorded agent run, exactly as it landed in Bento: the bottom of the stack, before any analysis or issue. The dashboard Runs page lists them with charts on top. The traces group reads the runs; the analytics group reads the totals and timeline above them. Once Bento analyzes a run it becomes a trajectory, which is where findings and issues come from. This page is the layer underneath. A run is a trace: a request your agent handled, captured whole. It’s made of spans, the steps inside it like an LLM call or a tool call, and carries a full body (the complete payload) and links to any issues it contributed to. A run’s status is error if at least one span reported an error, otherwise ok. The Runs table shows, per run: The charts come from analytics: a summary of totals (total runs and errors) and a timeline histogram of total/error counts bucketed by hour or day.

​
Commands

​
Browse runs

List the most recent runs:
Filter to what matters. --status is ok or error; --tag, --model, and --finding-kind repeat to pass several:
Look up a run by its run ID or trace UUID with --q, and bound the window with --start-time / --end-time:
Open one run:
Read its steps, then open the one you care about. To list only failed steps, pass the span-level --status ERROR (uppercase: span status, not run status):
Read the full payload, or see what the run is linked to:

​
Read the charts

The two analytics commands power the totals and the histogram. Both require --start and --end (ISO datetimes) and take the same filters as the list, so the numbers match the table. Totals over a window:
The timeline histogram. --bucket is hour (default) or day:
Scope the charts with the same filters as the table:

​
See also

Trajectories

What a run becomes after Bento analyzes it.

Issues

The tracked problems your runs roll up into.

Findings

The observations Bento extracts from these runs.