Skip to main content
Mirrors replays your AI agent’s real production sessions against your next change — a new prompt, tools, or model — and shows you exactly what would have broken. Nothing real gets touched. Your agent takes real actions on real systems, so testing changes against live production is slow, risky, and irreproducible. Mirrors ingests your agent’s traces and builds a runnable copy of its world: a seeded database plus bound tools. Agents replay against the mirror, never your real systems, so even destructive flows (refunds, deletes, sends) are safe to test.

​
How it works

1

Add two lines

The mirrorkit collector streams your agent’s traces to Mirrors. It works with traces from your agent framework or observability platform too.
2

Mirrors builds your agent's world

An isolated, runnable copy of the environment: a seeded database plus bound tools, each scored for fidelity against the real traces.
3

Replay any session against any change

From the dashboard, CLI, MCP client, or CI. Same session, two versions of the agent, one caught regression. Production is never touched.

​
Start here

Quickstart

Connect your agent and gate merges in CI in a few minutes.

How it works

Mirrors, fidelity scoring, deterministic seeding, and evals.

MCP server

Drive Mirrors from Claude Code, Cursor, VS Code, ChatGPT, and more.

API reference

The versioned /v1 API, authenticated by workspace keys.

​
What you can do with it

  • Catch regressions before they ship — replay real sessions against every change and see exactly what would have broken.
  • Reproduce the bug that paged you, on demand and byte-for-byte, via deterministic seeding.
  • Test risky and destructive flows (refunds, deletes, sends) safely against the mirror instead of live systems.
  • Gate CI on replays so every change is checked before it merges.
  • Measure whether an agent change is actually better with per-tool coverage and accuracy scores.
  • Drive mirrors from your own code over a versioned /v1 API authenticated by workspace keys.
Privacy by construction: the mirror keeps only the skeleton of which entities exist and how they connect. Every actual value is fabricated, so redacted sessions work fine.