Supported Public Beta scope

ScenarioDeck is designed for state-heavy web-application workflows where the useful reproduction can be represented through supported browser state, semantic actions, checkpoints, and captured HTTP behavior.

The current public release is a Public Beta. Platform availability is separate from feature scope: use scendeck.com/download to see which operating systems and architectures are currently published.

Good fit

Role, permission, feature-flag, account, form, validation, error, and empty-state workflows.
Manual Capture in ScenarioDeck’s managed browser.
The current direct automated-test Capture path for a selected supported CodeceptJS browser test.
Reopening a saved state against an explicit loopback/current-code target.
Full or partial Recorded Journeys with exact semantic steps and manual barriers where needed.
Captured supporting HTTP responses kept controlled while current code changes.
A selected supported dependency routed explicitly to loopback Local while the surrounding captured world remains replayed.
Browser console/page-error evidence captured under the selected evidence policy.
One-card encrypted sharing, local recipient import, and ordinary credential-free handoff.
Supported local authentication through ScenarioDeck-owned browser/profile and Auth Persona/Binding boundaries.

Known Public Beta limitations

External provider surfaces

ScenarioDeck does not yet promise deterministic capture and Frozen recreation of arbitrary third-party surfaces. Examples include:

cross-origin payment or booking forms;
support/chat widgets;
maps and geospatial widgets;
external media players;
OAuth/consent/auth widgets;
cross-origin iframes and popups with required provider state;
WebSocket or server-sent-event driven surfaces;
worker/service-worker-backed UI;
large media, upload, or download flows.

When a required external dependency cannot be safely captured, the State Card may be Partial, Unsupported, or stop on an exact dependency miss. ScenarioDeck does not silently fall back to the live provider or captured source system.

Cloudflare and anti-bot verification

Cloudflare, Turnstile, CAPTCHA, and similar anti-bot protected sites may fail to complete their verification flow inside the managed Capture browser. ScenarioDeck does not bypass or solve those controls. If the verification cannot complete, treat that site as unsupported for the current Public Beta workflow.

Backend and environment state

ScenarioDeck does not capture or recreate:

database snapshots;
server-memory snapshots;
queue or distributed-process state;
arbitrary backend virtualization;
a full production environment clone.

Browser and protocol boundaries

Confirm the workflow before relying on ScenarioDeck for SSR-specific behavior, GraphQL subscriptions, WebSocket/SSE streaming, OAuth/external redirects, service workers, file upload/download, large binary/media flows, DRM/WebRTC, or behavior that depends on arbitrary browser extensions.

ScenarioDeck does not attach to or copy your normal Chrome profile.

Sensitive values

Sensitive values are excluded by default.

For a supported protected candidate, the creator may explicitly keep the value in OS-protected machine-local storage. A retained protected value:

stays available only on that device;
requires explicit authorization for each reproduction run that uses it;
is not included in an ordinary State Card share;
blocks ordinary sharing while the saved workflow still requires that retained protected value.

If the creator confirms Discard, ScenarioDeck removes the protected local value, derives a sanitized saved Session, and turns that Journey point into a manual barrier. Ordinary credential-free sharing can then proceed when no other blocker remains.

Portable transfer of protected values is not part of the current Public Beta.

Automated tests

The current direct test-runner integration is CodeceptJS Run & Capture for one selected browser test. ScenarioDeck is not a generic test runner and does not claim direct support for arbitrary Playwright Test, Cypress, Selenium, CI-provider, or other runner workflows.

Fail-closed behavior

Unsupported behavior is reported explicitly. ScenarioDeck does not make a failed reproduction look successful by broadening network access, guessing ambiguous semantic targets, silently contacting the captured remote system, or claiming automatic root cause or bug fixing.