ScenarioDeck Desktop

Current Public Beta scope.

This is the boundary to rely on today: what the Public Beta ships, what it deliberately does not promise, and where it stops instead of guessing.

Availability

Public Beta availability

Windows
macOS
Linux

ScenarioDeck is in Public Beta. Installer packages will be published for the first public release; until then, no installer is available from this website.

Create

Create a State Card

Manual Capture

Open the application in the ScenarioDeck-managed browser
Reproduce the state you want to keep
Capture supported page, browser, form, storage, and API evidence
Stop and review before saving

Automated Test Capture

Choose one supported CodeceptJS browser test
Rerun it once under Capture
Save a State Card only when the expected failure reproduces

CodeceptJS is the currently shipping test-runner integration. Playwright Test, Cypress, Selenium, Jest, Vitest, CI providers, and arbitrary runners are not integrated today, and ScenarioDeck is not a generic test runner.

Review before you save

Selected saved state or checkpoint
Recorded Journey coverage — full, partial, or unavailable
Manual barriers in the Journey
Replayable API exchanges
Browser console and page errors
Optional description with Observed / Expected context
Protected-value decisions and sharing readiness

Developer access

Work from the State Card against current code

One unified Reproduce screen: pick the current loopback/local target, a saved state or Recorded Journey, a Development Profile or Clean Session, whether DevTools start open, and optional per-run protected-value authorization — then Reproduce.

Reopen a selected saved state against current localhost and current code
Replay a full or partial Recorded Journey
Pause at a manual barrier, then resume the remaining automatic steps
Use a persistent ScenarioDeck-owned Development Profile for everyday work
Switch to a clean isolated browser session when a clean run matters
Start with browser DevTools open in interactive Desktop
Keep captured supporting HTTP responses controlled
Stop on unmatched requests instead of silently contacting the source environment
Inspect Journey, console, network, application-state, and safety evidence
Create immutable supported response revisions and compare later runs where current behavior allows it
Reopen the same State Card after a restart

Handoff

The sender creates one encrypted temporary share
The recipient opens the generic secure landing
The recipient imports it locally without an account
The recipient uses the imported State Card under current access rules

Ordinary shares exclude machine-local protected values and Development Profile or authentication state
The sender can copy and revoke the link
Shares expire
Receiving and importing is free
Sharing is atomic and one Card at a time

Team workspaces, persistent shared libraries, RBAC, organization policies, and seats are future capabilities — one-card sharing is not a Team workspace or cloud execution.

Sensitive data

What happens to sensitive values

Sensitive values are excluded by default.

If you choose to retain a protected value locally

A supported protected value can be retained only when you explicitly choose it
A retained value is stored through the OS-protected machine-local boundary and is available only on that device
Each reproduction run requires explicit authorization before a retained value is used
Ordinary sharing is unavailable while a reproduction still requires retained protected data

If you discard it

Discard a protected value to remove it from the local protected reference path
The Journey gains a manual barrier for the missing step
Ordinary credential-free Share becomes available when no other blocker remains

Boundary

Not supported yet

Generic external surfaces

When a required dependency is not safely captured or supported, the Card becomes Partial or Unsupported, or reproduction stops on an exact miss. ScenarioDeck does not silently fall back to the live provider or source system.

Anti-bot protected sites

Cloudflare, Turnstile, and other anti-bot or CAPTCHA-protected sites may not complete verification inside the managed Capture browser
ScenarioDeck does not solve or bypass anti-bot controls

Data and environment boundary

Database snapshots
Server-memory snapshots
Arbitrary backend virtualization
Production-environment cloning
Universal reproduction of every app and protocol

Deferred product surfaces

Team workspace and shared organization library
Customer Capture SDK
Browser-extension capture in your own browser
Remote Capture worker
Native direct CI-provider integration
Runner integrations beyond CodeceptJS
Portable protected attachments
Full automatic application updater
Autonomous root-cause detection or bug fixing
Universal or expanded Verified reproduction semantics

Before you rely on it

Confirm the edge case first

SSR-specific behavior
GraphQL subscriptions
SSE/WebSocket streaming
OAuth and external redirects
Service workers
File upload and download
Large binary and media flows
DRM and WebRTC
Arbitrary browser extensions

Third-party checkout and payment forms, Support chat widgets, Maps and geospatial widgets, External media players, OAuth, consent, and auth widgets, Cross-origin iframes and popups, SSE/WebSocket-driven surfaces, Worker/service-worker-backed UI, Large media, download, and upload flows are not generally supported surfaces in this Beta.

Contact support

Vocabulary

One saved boundary, named clearly.

Setup: The supported browser, application, and API conditions ScenarioDeck can save and reopen — not a machine, database, or production environment.
State Card: A named product record that points to a State Capsule and may declare a non-secret Auth Persona requirement.
State Capsule: The credential-free technical artifact containing the portable captured application state behind a State Card.