Traces & sessions tables
The left side of a run’s Traces tab lists either its traces or its sessions. Switch with the Traces | Sessions toggle above the table. Both tables use the shared table controls for search, filters, sorting, and columns.
The traces table
Section titled “The traces table”One row per trace. Click a trace’s ID to open it on the right.
| Column | What it shows |
|---|---|
| Trace | The trace ID, with its status dot and, for a session’s task, a session button |
| Op name | The root span’s name, such as rollout |
| Step | The training step the trace was logged at |
| Started | When the trace started |
| Duration | How long it took |
| Turns | How many turns of the agent’s loop it ran |
| Spans | How many spans it has |
| Tokens | Its token count |
The Trace column is always shown and pinned; the rest can be removed, reordered, or resized.
Status
Section titled “Status”The dot before a trace ID shows status:
- Running — a pulsing green dot.
- Error — a red dot.
- Truncated — an amber dot.
- Cancelled — a gray dot.
- Completed — no dot.
Sessions
Section titled “Sessions”A trace that is one task of a session shows a speech-bubble button next to its ID (Session <id>). Click it to switch to the Sessions view with that task open, so you can step through the rest of the session.
Find traces
Section titled “Find traces”- Search (Search op names) matches the root span’s name as a regular expression. It ignores case unless you type an uppercase letter.
- Filter on the built-in fields — Op name (pick from the run’s op names), Status, Step, Started, Duration (ms), Turns, Spans, Tokens — or on any attribute your traces carry, such as a reward you set on the rollout’s root.
- Sort by any column, or by any attribute.
- Columns — add attributes as columns next to the built-in ones.
The search, filters, and sort are kept in the URL. Your column layout is remembered in your browser.
When the run has no traces yet, the table shows No traces for this run yet. When your search or filters match nothing, it shows No traces match.
The sessions table
Section titled “The sessions table”One row per session, built from the summaries the session writes when it ends. A session can write several — another process may continue it, or a scorer may re-score it later — and the table folds them into one row.
| Column | What it shows |
|---|---|
| Session | The session ID, with the status dot of its newest summary |
| Agent | The agent named when the session was opened |
| Reward | The session’s reward, from its newest summary that has one |
| Tasks | How many tasks the session had, across all its summaries |
| Step | The training step the session ended at |
| Ended | When the session ended |
Click a session ID to open its first task, then step through the rest with the task control. A session with no tasks recorded opens its summary instead.
Search (Search session ids), filters, sorting, and columns work as in the traces table, and the Session column is always shown. Next to attributes, columns and sorting offer Step and Ended, and filters offer Status, Step, and Ended.
Filters match each summary before the summaries are folded into sessions: a session is listed when any of its summaries matches, and its row is built from those summaries only. A filter on the reward can therefore list a re-scored session with its older reward.
A run without sessions shows No sessions in this run yet. When your search or filters match nothing, it shows No sessions match.
Live updates
Section titled “Live updates”While the run is active, both tables refresh every 15 seconds, so new traces and sessions appear as your agent logs them. If a refresh fails, the table keeps what it has and shows Couldn’t refresh with a button to try again.