---
title: "Explore the browser demo"
description: "Walk through the five-step prototype: choose a world, review the replica, run, inject a fault, and read the diagnosis."
canonical: "https://agenttwin.si/docs/prototype/"
---

# Explore the browser demo

Walk through the five-step prototype: choose a world, review the replica, run, inject a fault, and read the diagnosis.


The interactive prototype demonstrates the complete journey with invented companies, records, service behavior, and outcomes. All data is synthetic, and nothing connects to live systems.

<Card title="Open the interactive prototype" icon="lucide:play" href="/demo/" cta="Open the prototype">
  Select any example world. Each represents a hypothetical workflow for a potential customer, with entirely synthetic data.
</Card>

## The five-step walkthrough

<Steps>
  <Step title="Choose a world and discover its dependencies">
    Pick one of eight illustrative worlds and map its production stack before creating an isolated test environment.
  </Step>
  <Step title="Review what the test replica contains">
    See the declared boundaries — what is masked, blocked, or captured — before running anything.
  </Step>
  <Step title="Select a workflow and run its baseline">
    Run the workflow against a clean, repeatable starting state.
  </Step>
  <Step title="Inject a fault and run the same workflow">
    For example, commit a refund but discard the response, so the worker's retry has to be safe.
  </Step>
  <Step title="Read the failure diagnosis, then reset and rerun">
    Inspect the failed assertion and state difference, copy the fix prompt, and restore the same starting state for a regression run.
  </Step>
</Steps>

## Run it locally

The demo is a Next.js route in the same website app. Start the development server from the repository root.

```sh
cd /path/to/AgentTwin
npm ci --prefix web
npm run dev
# Open http://localhost:3000/demo/
```

## What the prototype does not do

<Warning>
  The fix prompt is a handoff for your coding agent or developer, with the observed failure and a suggested change. It does not inspect or patch customer code. The recovery preview uses a second scripted fixture. Refreshing the browser resets all session state.
</Warning>

- No credentials are requested and no provider APIs are called.
- No customer code is executed or modified.
- Company names are potential customer examples, not customers or partners. Stacks, records, and incidents are invented for demonstration.

For the current inventory of what exists, see [What exists today](/status).