> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oqoqo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Evals and Insights

> Evals score rubrics. Insights find frictions. Turn them on at launch or run them again later.

**Evals** and **Insights** are two separate ways Oqoqo reads a finished run. Enable either at launch. Run either again later without redoing the other.

Assign models under **Organization settings → Oqoqo AI features**. See [Oqoqo AI features](/setup/oqoqo-ai).

## Evals

Evals score each run against the task rubric. An automated judge marks every requirement pass or fail and explains why.

Open a run and select **Evals** for per-requirement verdicts.

Evals are judge-based. They are not a separate deterministic checker.

<img className="block dark:hidden" src="https://mintcdn.com/oqoqo/PXA7oNEwvzOgifCV/images/screenshots/run-evals-light.png?fit=max&auto=format&n=PXA7oNEwvzOgifCV&q=85&s=6216d4858e53ab85be1c8b70b90033eb" alt="Run Evals tab with a pass or fail verdict for each rubric requirement." width="2058" height="700" data-path="images/screenshots/run-evals-light.png" />

<img className="hidden dark:block" src="https://mintcdn.com/oqoqo/PXA7oNEwvzOgifCV/images/screenshots/run-evals-dark.png?fit=max&auto=format&n=PXA7oNEwvzOgifCV&q=85&s=17fda98fb948de54d48dbb58be26cfa5" alt="Run Evals tab with a pass or fail verdict for each rubric requirement." width="2058" height="700" data-path="images/screenshots/run-evals-dark.png" />

## Insights

Insights analyze saved traces and output. They find frictions, wasteful retries, and other failure patterns.

* **Run insights** — per-run analysis
* **Experiment insights** — one combined read across the experiment

Findings appear on the experiment **Frictions** tab. See [Frictions](/evaluation/frictions).

<img className="block dark:hidden" src="https://mintcdn.com/oqoqo/PXA7oNEwvzOgifCV/images/screenshots/frictions-light.png?fit=max&auto=format&n=PXA7oNEwvzOgifCV&q=85&s=419943bb7dcf1517d21be9a9204aa507" alt="Experiment Frictions table with clustered issues, descriptions, and recovery rates." width="1032" height="750" data-path="images/screenshots/frictions-light.png" />

<img className="hidden dark:block" src="https://mintcdn.com/oqoqo/PXA7oNEwvzOgifCV/images/screenshots/frictions-dark.png?fit=max&auto=format&n=PXA7oNEwvzOgifCV&q=85&s=5a5a20bbd4bc0fc53a0b06ae422a4e6d" alt="Experiment Frictions table with clustered issues, descriptions, and recovery rates." width="1032" height="750" data-path="images/screenshots/frictions-dark.png" />

## How they differ

|            | Evals                        | Insights                       |
| ---------- | ---------------------------- | ------------------------------ |
| Question   | Did the run meet the rubric? | Where did the agent get stuck? |
| Output     | Pass or fail per requirement | Frictions and patterns         |
| Depends on | Your rubric                  | Traces and output              |

You can run either without the other.

## Run again later

Once a run finishes, its recorded work stays fixed. Changing a rubric does not run the agent again.

If the rubric was wrong:

1. Fix the rubric.
2. Choose **Re-trigger Evals** to score the same recorded work under the updated requirements.
3. Or launch a new experiment when the task itself changed.

Choose **Re-trigger Insights** for a fresh friction analysis without changing rubric verdicts.

## Set this up

1. Connect providers under **Organization settings → Model providers**.
2. Assign **Run evals**, **Run insights**, and **Experiment insights** under **Oqoqo AI features**.
3. Turn Evals and Insights on at [launch](/experiments/launch-options), or trigger them from the experiment afterward.

<CardGroup cols={2}>
  <Card title="Oqoqo AI features" icon="sparkles" href="/setup/oqoqo-ai">
    Assign the AI feature models.
  </Card>

  <Card title="Frictions" icon="bolt" href="/evaluation/frictions">
    Use Insights findings to decide what to fix.
  </Card>
</CardGroup>
