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

> ## Agent Instructions
> To set Ambral up in a project, run `npx ambral@latest skill install` in the project's root. It installs Ambral's skill, matched to the CLI's version, and the skill says how to do everything these pages describe with the `ambral` CLI. Prefer it to working from these pages. Never ask anyone for an Ambral API key, and never handle one: the person creates it in the web app and stores it where their app reads its secrets.

# Report your own offline suite

> Keep running your own eval suite where it runs today, and report each time it runs to Ambral as an offline run.

A team that tests its agent with a suite of its own keeps running it where it runs today, on CI or a laptop, and
the suite reports to Ambral as it runs. Each time it runs is an **offline run**: the suite runs each scenario
whole, in its own environment, and reports its scores, while the agent's model calls go through the Gateway,
which serves them with the model the run chose and records them.

A [shadow eval](https://docs.ambral.ai/guides/shadow-evals) scores one reply at a time on recorded production sessions. An offline run
scores whole sessions, each on the candidate's own path, so it shows what a shadow eval can't. Most agents should
have both: see [Concepts](https://docs.ambral.ai/concepts.md#replay-runs-and-offline-runs).

A suite reports through one of Ambral's SDKs: [TypeScript](https://docs.ambral.ai/sdks/typescript.md), for a Vitest suite, a script or
another test runner, and [Python](https://docs.ambral.ai/sdks/python.md), for a pytest suite, a script, a verifiers eval or a Harbor job.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.