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

# Continuous evals

> Run your agent against hosted mock worlds and detect regressions in CI.

Ressl evaluates your agent by running a dataset of tasks against fresh mock
worlds. It grades the final state of each world, compares the result with a
previous run, and reports regressions in CI.

You connect your agent through a `runAgent(task)` function. The
[`@resslai/eval`](https://www.npmjs.com/package/@resslai/eval) SDK handles the
rest: it pulls tasks, provides an MCP server for each task, and reports when the
agent finishes.

## How it works

1. CI starts an evaluation for the current commit.
2. Your worker pulls tasks from the evaluation queue.
3. Each task includes a ticket and an isolated MCP server.
4. Your agent uses the MCP tools to complete the ticket.
5. Ressl grades the final state and deletes the mock world.
6. Ressl compares the run with the previous run for the same dataset and model.

<Note>
  The worker only makes outbound requests. You do not need to expose a server,
  and your model credentials stay in your environment.
</Note>

## What gets measured

Ressl calculates two metrics from the final state of each mock world:

| Metric         | Meaning                                         |
| -------------- | ----------------------------------------------- |
| **Resolution** | Percentage of tasks that passed every assertion |
| **Assertions** | Percentage of individual assertions that passed |

The commit check fails if either metric is lower than the previous run for the
same dataset and model.

<Note>
  Ressl does not choose or run your model. Set the SDK's `model` option to the
  same model identifier used by your agent. Ressl uses this value to group
  comparable runs.
</Note>

## Datasets

A dataset is a collection of tasks and grading assertions. You can find your
datasets in the **Datasets** tab of the
[Ressl console](https://simulation.ressl.ai).

Use the dataset slug when starting a run. You can evaluate the full dataset or
provide specific task IDs for a smaller smoke test.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/evals/quickstart">
    Install the SDK and add evaluations to CI.
  </Card>

  <Card title="SDK reference" icon="code" href="/evals/reference">
    Review the worker options, task fields, and events.
  </Card>
</CardGroup>