ScenarioDeckDownload

For coding agents

Your agent already has the code. Give it the state.

Give a coding agent a complete reproduction recipe and browser access, and it can often follow the steps. The missing piece is the state that bug reports leave out. A State Card gives the agent a reviewable, reproducible starting point through MCP.

See the MCP workflow

Premise

Agents can already follow reproduction steps.ScenarioDeck adds the captured state they should not have to infer.

A recipe is not the captured state.

A written issue can be useful without describing everything that made the moment reproducible. State Cards make the known context explicit within the supported capture scope.

Description-only

Log in as Manager. Open account 42. Go to Billing. Click Calculate.

A useful recipe that can still leave relevant state to reconstruct.

State Card

Open the exact captured state before changing code.

  • tenant and account context
  • permissions and feature flags
  • browser storage and route/query state
  • captured API responses and request order
  • explicit auth requirement

Frozen world

The value is not basic browser automation. It is rerunning code changes against the same surrounding application world instead of comparing two reconstructed environments that may have drifted.

Description-onlyreconstruct → state may drift → change code → reconstruct again

ScenarioDeckState Card → Frozen world → change code → reopen the same State Card

Keep the context. Change the selected dependency.

Hybrid work keeps selected supporting routes or dependencies replayed while the dependency under active development points to approved localhost. It is an explicit boundary, not a promise to virtualize every backend or production system.

/api/me
Replay
/api/account
Replay
/api/catalog
Replay
/api/calculate
Local

One State Card. The same runtime boundary.

MCP gives the coding agent a safe way to use the same State Card and runtime controls that support manual local work. The agent does not receive a separate category of access.

  1. 01State Card IDStart from the referenced saved revision.
  2. 02Inspect and open via MCPRead structured evidence and the active boundary.
  3. 03Set selected route LocalKeep supporting context replayed when appropriate.
  4. 04Change current codeWork in the agent's normal coding environment.
  5. 05Reopen and compareUse the same saved revision for the next run.

Ground truth does not mean secret access.

Agents receive safe State Card/runtime metadata and actions. Raw passwords, tokens, and Auth Bindings are not handed to the agent.

If an open needs authentication, ScenarioDeck keeps that as an explicit human-mediated auth-required state. Frozen safety, redaction, and live-origin restrictions do not change for agent opens.

Give your coding agent the reproduction, not the reproduction steps.

Use a State Card as the bounded starting point for the next local debugging loop.

See the local-first workflow