ScenarioDeck

Capture the setup once. Reopen it against current code.

ScenarioDeck records the supported browser and API conditions behind a useful web-app setup or bug, saves them as a State Card, and lets you return to the same reproduction without rebuilding it every time.

Get started · Read the CLI reference

ScenarioDeck is currently distributed as a Public Beta. Use scendeck.com/download for the exact platforms and architectures available in the current release.

The current workflow

Capture Session
→ Review / redact / curate
→ Save State Card
→ Reproduce Saved state or Recorded Journey
→ change current code or one supported response
→ save revision
→ reproduce / compare

A current State Card points to a bounded Capture Session containing safe semantic actions and meaningful checkpoints plus immutable State Capsule material for supported browser/API replay.

Send the reproduction

One supported State Card can be shared through a temporary encrypted link:

sender shares State Card
→ recipient imports it locally
→ recipient reproduces it against their own current code

No ScenarioDeck account or Developer license is required merely to send, receive, import, or inspect one card. Ordinary sharing excludes machine-local protected values, browser-profile data, local Auth Bindings, and local sign-in state. Developer access becomes relevant only when the recipient chooses to execute the saved reproduction against current code.

This is one-card handoff, not a Team workspace or cloud-hosted execution environment.

What ScenarioDeck supports today

• bounded semantic Capture Sessions with checkpoints;
• manual Capture plus the current direct CodeceptJS Run & Capture path;
• mandatory Review before a State Card is saved;
• Saved state and full/partial Recorded Journey reproduction against an explicit loopback target;
• Development Profile or Clean Session as the browser-session choice;
• DevTools in the interactive developer workflow;
• fail-closed captured-response replay with explicit loopback Local routing for supported dependencies;
• browser console/page-error evidence under the selected evidence policy;
• bounded redacted JSON response editing with immutable revisions;
• reopen and safe run comparison;
• machine-local Auth Personas/Bindings separate from portable artifacts;
• explicit protected local-value retention with per-run consent where supported;
• encrypted temporary State Card sharing and local import;
• CLI and MCP over the same trusted runtime and access policy.

Read supported Public Beta scope before using ScenarioDeck with a new app.

What ScenarioDeck does not do

ScenarioDeck does not copy a backend database/server environment, use your normal Chrome profile, silently retain or transfer sensitive values, provide generic session replay/observability, or claim automatic root cause/fixes.

Arbitrary third-party surfaces, anti-bot protected sites, broad streaming/media protocols, and direct test-runner integrations beyond the current supported CodeceptJS path have additional Public Beta limitations described in supported scope.

Access

Free Capture
Capture → Review → Save/manage → Share
Receive → Import → Inspect

Developer trial / paid Developer
Reproduce → Experiment → Revision → Compare

Free Capture has no arbitrary card/project/monthly-capture quota and does not consume the 14-day Developer trial. The trial starts only through an explicit Developer operation.

Release availability

A platform is part of the Public Beta only when the download page shows a real versioned installer that passed its release checks. An unavailable platform is intentionally not offered as a public installation target.