A reproducible browser-agent demo

A saved click still needs a read-back.

Choose the test that answers your question. The online fixture shows a synthetic record surviving a reload. The local runner checks recovery across two separate processes.

In this browser

Inspect one synthetic save

Save a sample draft, reload the page, and compare the stored title, body, and save count. The fixture keeps its record in this browser's local storage.

Open the synthetic fixture

It tests page persistence and read-back. It does not run an agent or call a model.

On your machine · Node.js 20+

Resume in a new process

The first process saves and verifies one synthetic record, writes a checkpoint, and exits. The second process restores the fixture and confirms the save count remains 1 without dispatching the completed action again.

From the repository root:

npm install
npx playwright install chromium
npm run demo:prepare
npm run demo:resume

The local runner uses loopback port 4179 and writes synthetic evidence to the ignored runs/ directory.

Read the full recovery steps and limits

What this demonstrates

The browser fixture and local runner use deterministic host code and synthetic data. They make no model calls and use no social or customer accounts.

These checks demonstrate the included persistence and recovery paths. They do not measure model behavior, production crash consistency, or compatibility with Muse, Grok, or Codex. See the recorded verification for test scope.

If a save count or restored record differs from these steps, report a synthetic failure case with the steps and the value you observed.