ScenarioDeck
Download

Open the State Card against your current localhost.

ScenarioDeck gives a difficult application state a named, reviewable entry point. Return to the useful context without rebuilding the setup from a checklist.

State Card

01PrepareOpen the app in the managed browser.
02CaptureReproduce the difficult state.
03ReviewInspect evidence and exclusions.
04SaveKeep a named State Card.
05ReproduceOne launcher, your current code.

A state you can return to.

The workflow is deliberate. Each step makes the resulting context easier to understand before it becomes part of your development work.

  1. 01

    Prepare and capture the difficult moment

    Open the application in the ScenarioDeck-managed browser, reproduce the state worth keeping, and capture the supported page, browser, form, storage, and API evidence — or rerun one supported CodeceptJS test under Capture.

  2. 02

    Review before you save

    Inspect the saved state, Recorded Journey coverage, replayable API exchanges, console evidence, and protected-value decisions before the State Card exists.

  3. 03

    Reproduce from one unified launcher

    Pick the current local target, the saved state or Journey, a Development Profile or Clean Session, and optional per-run protected-value authorization — then reproduce against current code while supporting responses stay controlled.

  4. 04

    Clean Session check

    When the verification surface is available in your build, check the exact State Card or revision in a fresh context.

What runs when you capture and open.

ScenarioDeck Desktop provides the managed browser boundary around the local workflow. It is not a browser extension or a copy of your app's backend.

Capture and reproduction run in the ScenarioDeck managed Chromium browser boundary — not a browser extension, not a copy of your app's backend.

Normal Beta Capture does not require a customer Capture SDK or app-code instrumentation.

When authentication is needed, an explicit machine-local protected-value decision is separate from ordinary capture.

See current Beta scope

Agent-first branch

The same State Card works for an agent-first loop.

Coding agents can already reproduce many browser bugs from text. The ScenarioDeck debugging skill captures the first faithful result, then reuses it instead of reconstructing the setup after every edit.

See the agent workflow

Reusable reproduction

01CaptureText bug report → agent reproduces under Capture → confirmed State Card
02Iteratechange code → reopen → compare → repeat
03FallbackStart fresh only for a stale Card, intentional new state, unsupported path, or explicit request.

Make the dependency boundary visible.

Keep the surrounding world stable while you choose exactly which route should use local code.

Supporting dependency
Frozen
Route under change
Local
Unexpected request
Block

A better starting point for local work.

A State Card is not a promise to recreate every system. It is a bounded, inspectable way to return to the application context you actually need.

Read the security approach