Prerequisites
- Finished experiments with Insights on, because most frictions come from Insights. If an experiment ran with Insights off, select Run insights on it first.
- Access to the place where the fix goes: your product, your tool, your custom agent, or the task.
Steps
1
Open the friction list
Open Analyze → All frictions for the whole project, or the Frictions tab of an experiment, task, tool, treatment, machine, agent, or schedule. To start from a difference instead, open the experiment’s Comparisons tab: its Brief lists the frictions seen with the side that did worse.
2
Filter by where you can fix it
Fix Machine or Task quality frictions first, because they make the other results unreliable. Then, under Where to fix, choose where you can act: Product, Custom agent (shown when your custom agent has frictions here), Setup, or Agent behavior, and narrow the list with Family and Recovery. The list starts sorted by Unrecovered runs, so problems that agents never got past come first.
3
Read the top friction
Select the top friction to see What goes wrong, Why it matters, and the Suggested fix with where to make it. When the agent also contributed, What the agent did follows the fix. Where it happens most, Rate by treatment, and Rate by agent show whether some agents or treatments avoid it.
4
Read the traces at the cited steps
Under Recent evidence, each run shows what happened, with quotes from its trace. Select the step link to open the run’s Traces at the first step that the friction cites, and read the steps around it to confirm the cause. The Runs section lists every run with the friction.
5
Copy it as Markdown
Select Copy as Markdown to copy where to fix the friction, what goes wrong, the suggested fix, where it happens most, three recent runs with links to their traces, and the friction’s
frc_ ID. Paste it into an issue, or give it to the AI assistant that you use in your product’s or your custom agent’s repository. Copying doesn’t change anything in Obss.6
Fix it in the right place
7
Launch again and confirm
Open the experiment where the friction occurred and select Launch again. When it finishes, open the friction from the new experiment’s Frictions tab. If the fix worked, the friction has fewer runs, or it no longer appears for that experiment.
Interpret the results
A fix worked when the friction has fewer runs in the new experiment and more trials pass on its Matrix. Frictions keep their IDs across experiments, so you can follow one over time.From the CLI and the plugin
An AI assistant with the Obss Plugin or the CLI can do this whole guide in your repository. When it reads a friction, it gets the same fields as Copy as Markdown.
For example, list the unrecovered product frictions, then read one friction’s counts in the new experiment:
Other ways to run it
- Fix one tool. Open the tool under Manage → Tools and select its Frictions tab to see the frictions of every run that used it.
- Fix your custom agent. Choose Custom agent under Where to fix.
- Use Ask Obss. Ask Obss can explain a friction and compare it with the code in a public GitHub repository.
- Make sure it stays fixed. Schedule the experiment to catch the friction if it returns. See Track results over time.
