One-card handoff is not a Team workspace.
Team collaboration will add organization-level controls without changing the free, temporary State Card handoff.
StatePort for web developers
Stop rebuilding the bug setup.
Got to the bug after choosing the right role, changing permissions, and reaching a stubborn error state? Capture a supported setup, review it, and save a State Card. Then reopen it against a running local app and your current code.
StatePort 1.0.0-beta.107 Public Beta — macOS arm64 (DMG), Windows x64 (EXE), Linux x64 (DEB). Unavailable: unlisted packages. No card is required to download; Free Capture remains available after trial or paid access ends.
A familiar debugging loop
Without StatePort
- Open the team settings
- Select the Manager role
- Enable project export
- Submit the permissions form
- Reach the validation error
With StatePort
- Open “Manager permissions” 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. StatePort turns the supported ones into one reopenable starting point.
Capture onceSave the setup that makes the bug happen.
Reopen when supportedRun the prepared Card against a selected target and current code.
Change what mattersKeep supporting API behavior stable while you fix the part under investigation.
Save the setup, not a checklist.
StatePort saves the reusable setup as a State Card— a prepared 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
workflow illustrationSaved State Card
- Route
/team/permissions - Supported state
Manager · export enabled - Captured response
GET /api/permissions · 200
Your running local app
- Code
- current working tree
- Target
- selected loopback route
- Auth
- separate local sign-in, when required
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 chooses a target and local authentication when needed. Ordinary shares do not include login secrets. Expiry or revocation stops future link downloads; it cannot erase a copy already imported or downloaded.
A recipient imports the shared State Card locally, then opens it against their own current code. Receiving and importing do not require an account. Opening it against current code requires Developer access.
Start where the bug is
Testing the bug? Capture is free.
Capture, review, and keep supported State Cards without a card or trial countdown. After email verification, 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. StatePort gives you a prepared starting point while your local code keeps changing.
Saved starting material. Current code. Observed result each run.
- 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
Choose the running local app and target; configure separate local authentication when required.
- 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
Work with your coding agent
Reproduce once. Verify the same case.
Give your agent focused source context and reusable browser cases. Your chosen agent changes the code; StatePort provides context, runtime actions, and evidence to check the result on current code. Work directly in Desktop whenever you prefer.
- Fix & VerifyReproduce the bug, change the code, then check the same saved case again.
- Check ChangesCheck relevant saved cases after an edit. See observed findings and coverage gaps.
- Harden CaseTry a few justified JSON data edge cases around one Card, keeping the original unchanged.
- Not every fix needs a recording.Source lookup needs no Capture. Helper availability depends on runtime and platform; browser workflows also require permissions.
Save the setup, not your secrets.
StatePort 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.