One-card handoff is not a Team workspace.
Team collaboration will add organization-level controls without changing the free, temporary State Card handoff.
ScenarioDeck for web developers
Reproduce the bug once. Never rebuild the setup again.
Got to the bug after logging in as the right role, filling a form, and hitting an awkward API response? Capture that setup once. Open it later against your current localhost and keep working on your current code.
No card required. Free Capture remains available after a trial or paid access ends.
A familiar debugging loop
Without ScenarioDeck
- Sign in as the account owner
- Open the billing screen
- Turn on the feature flag
- Fill the payment form halfway
- Wait for the declined-card response
With ScenarioDeck
- Open “Payment declined” setup
How it works
Capture the setup. Open it against current code.
- CaptureRoute, safe browser context, selected API responses
- State CardOne saved starting point for the setup you need
- OpenCurrent localhost and current code
Not a screen recording. Not a test script. A reusable application state you can reopen against your current code.
The pieces already exist. ScenarioDeck turns the supported ones into one reopenable starting point.
Capture onceSave the setup that makes the bug happen.
Open anytimeReturn to it against your current localhost and current code.
Change what mattersKeep supporting API behavior stable while you fix the part under investigation.
Save the setup, not a checklist.
ScenarioDeck saves the reusable setup as a State Card— a one-click way back to the app state you need. It keeps the route, relevant browser context, and selected API behavior together so you do not have to recreate the same roles, forms, flags, and edge cases.
State Card
ready to open- Route
/account/preferences - Browser state
reviewed state - API responses
GET /api/profile · 200 - Local code
current localhost
One State Card, two local workflows
Share the reproduction, not the instructions.
When the next step is handoff, send the State Card instead of a long checklist. The recipient imports it locally, then opens it against their own current code. Ordinary shares do not include login secrets and can expire or be revoked.
A recipient imports the shared State Card locally, then opens it against their own current code. Receiving and importing do not require an account.
For coding agents
Your agent found the bug. Keep the state it found.
Coding agents can already follow a competent bug report. ScenarioDeck turns the first faithful reproduction into a State Card, so the next code change starts there instead of rebuilding the setup.
See the agent workflowStart where the bug is
Testing the bug? Capture is free.
Capture, review, and keep supported State Cards without a card or trial countdown. Start the full 14-day Developer trial explicitly when you are ready to reopen and work from them against current local code.
Capture it. Open it. Keep working.
Start from a real setup you already reached. ScenarioDeck gives you a reliable way back while your local code keeps changing.
Same starting state. Current code. Every iteration.
- 01
Get the app into the setup you need
Use the role, form progress, and edge case that make the work real.
- 02
Capture it once
Review the route, safe browser context, and replayable API behavior that make it reusable.
- 03
Open it against localhost
Return to the same useful setup while your current code runs locally.
- 04
Change code and reopen the same setup
Keep iterating without reconstructing the path to the bug every time.
When you need more control
Supporting API behaviorReplay / FrozenService or route under investigationLocalUnexpected request that must not escapeBlockFresh proof of the saved setupClean Session
For coding agents
Reproduce once. Debug repeatedly.
Agents can already reproduce many browser bugs from a competent description. With the ScenarioDeck debugging skill, the first faithful reproduction becomes a State Card and later fix iterations reopen that exact state through MCP.
See the agent workflow- First faithful reproductionWrong or inconclusive attempts are not saved as the authoritative bug Card.
- Reopen after every changeThe same Card drives repeated current-code and compare loops without rebuilding the original setup.
- Safe handoff boundaryMCP provides safe state and runtime controls without passing raw passwords or tokens.
Save the setup, not your secrets.
ScenarioDeck can save the app setup you need without making login credentials part of that saved artifact. Credentials stay behind a separate local authentication boundary.
Read the security approachPlanned
Team workspaces are still ahead.
One State Card can now move between developers. Shared workspaces, members, organization policies, and persistent team libraries remain future capabilities.
Reproduce it once. Open it again when the code changes.
Keep the difficult setup. Spend your time fixing the code.