Mirra is in private beta. The steps below work today — the CLI installs, a local stub runs, and
mirra up provisions test mirrors. To provision real mirrors against the hosted control plane you need an access token — request one here.1. Install the CLI
- npm
- pnpm
- npx (no install)
2. Authenticate
~/.config/mirra/credentials. Log out any time with mirra logout.
3. Boot your first session
Runmirra up from any project directory:
package.json, detects the vendor SDKs you depend on, and provisions a mirror for each. A short-lived TLS proxy routes api.stripe.com, api.resend.com, and api.twilio.com to the mirror URLs transparently — your existing SDK clients don’t need URL changes.
4. Make a request
In a second terminal, use your application as normal:api.stripe.com was never called. No real money. No real account state. Yet the SDK client behaved identically: request shape, response shape, latency profile, error model.
5. End the session
Ctrl-C in the session terminal. Ephemeral mirrors tear down instantly; their state is gone.What to explore next
Run a scenario
Write a markdown scenario and run it with
mirra run scenario.md.Drop into Vitest
Wrap your existing tests with
withMirra() — zero code changes to the tests themselves.Wire up your coding agent
Point Claude Code or Cursor at Mirra’s MCP server.
Understand mirrors
How mirrors differ from mocks, sandbox modes, and shared staging.