# Read results - Obss

Read results
Read results
Read an experiment’s Matrix, Comparisons, Frictions, and Runs, compare runs side by side, and download a run’s trajectory.
Results show which treatments helped, where agents got stuck, and what each agent did. Every experiment has four result tabs:
Matrix
,
Comparisons
,
Frictions
, and
Runs
.
Read an experiment in this order
Start with the whole experiment and narrow down:
Matrix
shows which task, agent, and treatment combinations passed, and what they cost.
Comparisons
answers the experiment’s question first: who did better, and how sure that is. When Insights has reviewed the runs, the
Brief
under a difference lists the frictions seen with the side that did worse.
Frictions
ranks the problems agents hit, starting with the ones that stopped the most runs.
Runs
lists every run. Open a failed run, or one with a friction, to read its
run details
.
Pass rate and lift
Pass rate
is the share of runs that passed the task’s rubric in
Evals
. A blocked run wasn’t evaluated, so it doesn’t count. Each
trial
is one run, so a cell’s pass rate is over its trials. Agents don’t give the same result every time, so repeats give you a pass rate you can trust.
Lift
is the difference in pass rate between a treatment and the
baseline
you chose
at launch
.
Matrix
shows no lift number, so compare cells:
Set the
Matrix metric
to
Evals
.
Find the treatment’s cell and the baseline’s cell for the same task and agent.
Hover over each one to see how many trials passed.
For example, if the baseline cell says “1 of 4 trials passed” and the treatment’s cell says “3 of 4 trials passed”, the treatment’s lift on that task is 50 percentage points (25% to 75%).
Positive lift can mean that your skill, MCP server, CLI, or SDK helped, but agents don’t give the same result every time, so a small gap doesn’t show that one side is better.
Comparisons
tells you whether the difference holds up. For the full workflow, see
Measure a tool’s impact
.
Matrix
Matrix
is a heat map of the experiment. By default, rows are tasks and columns are agent and treatment combinations. Each cell shows one metric, averaged over its trials. Pick the metric with
Matrix metric
:
Metric
What a cell shows
Evals
The pass rate. It comes first when the experiment ran Evals.
Steps
Average steps per run
Tool calls
Average tool calls per run
Treatment use
The share of trials in which the agent called a tool from the treatment. Calls made inside scripts aren’t visible, so this is a lower bound.
Frictions
Average frictions per run
Tokens
Average tokens per run
Cost
Average cost per run. A cell whose costs come from more than one source shows
Mixed sources
.
Duration
The agent’s working time, without machine setup or other run overhead
Hover over a cell for details. Pass rate and treatment use cells say how many trials counted, for example “3 of 4 trials passed”. Other metrics show the average, minimum, maximum, and spread. A
*
marks a cell where some trials didn’t finish or didn’t report the metric.
Above the grid, one line gives the sentence that opens
Comparisons
, such as “Stripe CLI did better than Raw Agent on all 7 tasks.” When the experiment has a
Brief
about a difference, the line starts with
Brief
and links to
See the differences
. Otherwise it starts with
Comparisons
and links to
See the comparison
, or to
See all N comparisons
when there are two or more. When Comparisons has nothing to compare, there’s no line.
In this transposed view of the
Stripe interface evals
experiment,
Raw Agent
fails four of the five tasks, and the Stripe CLI rows pass more of them.
Control
What it does
Search tasks
Finds tasks by name
Evals
,
Treatment (toolset)
,
Agent
Keep only the tasks with those results, or only those columns.
Evals
takes
Pass
,
Fail
, and
Run blocked
.
Transpose
Swaps the axes, as in the example
Runs
Runs
lists every run with its task, treatment (toolset), agent, trial, Evals result, and metrics. Select a row to open the run. The
Treatment use
column says whether the agent used the
treatment
. A blank cell means the run has no
run profile
.
Search runs by task, agent, or model
finds runs by name.
Evals
,
Status
,
Treatment (toolset)
, and
Agent
filter the rows.
Treatment (toolset)
appears when the runs used more than one treatment, and
All runs
adds an
Experiment
filter.
Best trials
keeps the best trial of each task, treatment, and agent.
To keep a copy of what an agent did, open the run and use its
⋯
menu
.
Compare runs side by side
To see how different agents or treatments handled the same work, select two or three runs on
Runs
, then select
Compare
. Each run gets a column with its
Traces
,
Output
, and
Evals
, and each
Traces
column starts with the
Timeline
and the
Run profile
.
You can also select
Compare
on an open run. It stays the first column, and you can add up to two more runs. Its other trials and other runs of the same task come first, and you can search the whole project.
Find results across the project
The
Analyze
group in the sidebar collects results from every experiment:
Page
What it lists
All experiments
Every experiment, with its status
All runs
Every run, with the same filters as an experiment’s
Runs
tab
All frictions
Every
friction
in the project
Ask Obss
, or your AI assistant through the
Obss Plugin
, can summarize a Matrix, the top frictions, or a single run.
From the CLI and the plugin
Task
CLI
Plugin (MCP)
Check an experiment’s progress
obss experiments status
get_experiment_status
Summarize results or compare treatments with the baseline
obss results analyze
analyze_results
Read the Brief
obss experiments brief
get_experiment_brief
Check whether a difference holds up
obss evals compare
get_evals_comparisons
List and filter runs
obss runs list
list_runs
Read a run’s profile
obss runs profile
get_run_profile
Read a run’s steps
obss runs trajectory
get_run_trajectory
Read a run’s raw transcript
obss runs transcript
get_run_transcript
Read a run’s answer and files
obss runs output
get_run_output
Query results as rows
obss data query
query_data
Next steps
Comparisons
Check which differences between treatments and agents hold up.
Frictions
Find the problems agents hit and where to fix them.
Run details
Read a run’s traces, output, and profile.
Evals
Learn how Evals score each run.
Tags
Comparisons
Powered by
This documentation is built and hosted on Mintlify, a developer documentation platform