/runs/{id} lands on the run’s project with that run selected. A run filed under no project keeps a page of its own.
Experiments
An experiment’s header carries its name, an Experiment badge, its tags and its question. The center compares its runs, and the context pane holds its Summary, Notes and Files. Its runs are listed under it in the explorer; selecting the experiment shows all of them.Conclusion
An experiment can carry a conclusion: its answer to the question. It shows beside the header, under a Conclusion heading that names who wrote it (Conclusion · <name>). A person or their agent writes it; one written by the retired overview writer reads Conclusion · AI until someone replaces it. To add the first one, use the Add conclusion flag in the header; the text itself is the edit target after that.
Compare
The experiment’s runs share one set of charts, with two views behind one toggle:- Line charts
- Parallel coordinates
One chart per metric. Each run keeps a stable colour across every chart, and the legend and the explorer’s eye controls hide and show runs across them all. A hidden run stays listed so you can bring it back.
Versions
Freezing an experiment pins its run set in an immutable version, which is what a citation points at. Freeze from the CLI or SDK:Runs
A selected run’s Metrics fill the center. RL runs add Compute and Rollouts views beside it. The other tabs sit in the context pane; Config, Data, Related, Trials and Sessions appear only when the run has something for them:
A run has no Summary of its own.
Related counts every loaded child, including descendants summarised below a direct child. Ancestors and the run itself are not listed — the header and breadcrumb already establish that context.
Steps and diffs
/runs/{id}/steps/{step} opens one step: its metric points, its record of non-numeric values, and any sandbox diff captured at that point. /runs/{id}/diff compares captured working-tree state.
Trials
/runs/{id}/trials/{trial} is a first-class entity page with the stored title (editable by members), the trajectory expanded into turn and tool-call spans where the format was recognised, the reward, and the captured files.
Sessions
A session page carries the session’s full transcript, in order. Sessions attributed to a project or run appear on its Sessions tab, which is what keeps “why was this launched” answerable.Refresh behaviour
Running entities poll; settled ones do not. A page does not silently swap out the data you are reading — an obsolete request triggered by a workspace or query change is aborted rather than allowed to answer for inputs you have already left.Charts in detail
Zoom, settings, expression panels and the captured rows behind a curve.