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

# Getting started (for agents)

A mirror is a digital twin of the backends an AI agent talks to. It is built from the agent's production traces (plus optional tool code, schemas and specs) and served as a twin your agent can call instead of production.

Concepts: a mirror (one agent's backends), a build (an immutable artifact from a frozen snapshot of the inputs), the active build (what the twin serves), the twin (a running task with sessions), a session (one isolated world your agent calls tools in), fidelity (how closely the twin answers like production, measured by replaying traces), drift (per-tool reasons the twin differs, each with a lever that fixes it), config (versions of knobs and overrides), proposals (drafted repairs you accept or reject).

Flow: identity\_whoami; mirrors\_builds\_intake with traces (see mirrors\://formats/inputs) or stream traces with a collector to /api/collect; poll mirrors\_builds\_get; mirrors\_get for the headline; runtime\_twin\_start; runtime\_console\_open and runtime\_console\_invoke to call tools, or open sessions over /v1 with an API key; mirrors\_builds\_drift and improve\_proposals\_draft to improve; improve\_review\_list for what agents changed.

Names: tools are the service verbs with dots as underscores; the same verbs back the web app, the CLI and this server.

This page is also the MCP resource an IDE agent reads; generated by `pnpm docs:generate`.