Team handoff is upcoming.
When collaboration ships, the goal is a reviewable developer artifact instead of a long reproduction checklist.
Save a difficult application state once. Reopen it against your current localhost in one click — with the route, browser state, authentication context, and API world already in place.
Installers are published independently of purchase.
/account/preferencesreviewed stateGET /api/profile · 200current localhostRoles. Accounts. Feature flags. Forms. Browser state. API edge cases. ScenarioDeck saves the useful application state so you can return to the code instead of rebuilding the setup.
A State Card is a named, reusable entry point to the application state you need for development work.
Save the route, safe browser state, and replayable API world.
Inspect the capture and exclusions before it becomes reusable.
Keep supporting dependencies frozen and route selected work Local.
Use a Clean Session when you need reproducibility evidence.
Inspect what is captured. Know what is excluded. Credentials stay separate from portable application state unless explicitly attached through a supported protected test-auth flow.
Read the security approachPlanned
State Card sharing and customer-bug handoff are future capabilities, not part of the current local Alpha workflow.
When collaboration ships, the goal is a reviewable developer artifact instead of a long reproduction checklist.
ScenarioDeck turns application state into a reusable developer artifact.