Team handoff is upcoming.
When collaboration ships, the goal is a reviewable developer artifact instead of a long reproduction checklist.
Stop rebuilding state. Start where the bug is.
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.
State Card
ready to open- Route
/account/preferences - Browser state
reviewed state - API responses
GET /api/profile · 200 - Local code
current localhost
Capture, review, openKeep the useful state, not a setup checklist.
Frozen / Local / BlockMake the dependency boundary explicit while local code changes.
Clean Session verificationCheck the exact State Card or revision in a fresh context.
Your bug is not the hard part. Rebuilding the setup is.
Roles. 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.
- Access and feature context
- In-progress form state
- Relevant API responses
How ScenarioDeck works
A State Card is a named, reusable entry point to the application state you need for development work.
Supporting APIFrozenSelected endpointLocalUnexpected requestBlock
- 01
Capture current state
Save the route, safe browser state, and replayable API world.
- 02
Review what is stored
Inspect the capture and exclusions before it becomes reusable.
- 03
Open against localhost
Keep supporting dependencies frozen and route selected work Local.
- 04
Verify the exact revision
Use a Clean Session when you need reproducibility evidence.
For coding agents
Your agent already has the code. Give it the state.
Coding agents can follow reproduction steps, but issue descriptions rarely contain the entire application state. Give the agent an exact State Card through MCP so it can reopen the captured world while your current local code changes.
See the agent workflow- Exact state, not inferred setupRoute, browser state, and supported API context come from the State Card.
- Frozen experimentsKeep the surrounding supported world stable while code changes.
- MCP-nativeUse the same ScenarioDeck runtime and safety boundaries as Desktop and CLI.
- Repeatable compare loopReopen the exact saved revision instead of rebuilding the environment again.
Portable state, not portable secrets.
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
Send the state, not the steps.
State Card sharing and customer-bug handoff are future capabilities, not part of the current local Alpha workflow.
The exact state. Your current code. One click.
ScenarioDeck turns application state into a reusable developer artifact.