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

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.22 Public Beta — macOS arm64 (DMG) and Linux x64 (DEB). Unavailable: Windows and unlisted packages. No card is required to download; Free Capture remains available after trial or paid access ends.

A familiar debugging loop

Without StatePort

With StatePort

How it works

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.

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.

Saved State Card

/team/permissionsManager · export enabledGET /api/permissions · 200Your running local app

One State Card, two local workflows

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

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.

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.

Use the role, form progress, and edge case that make the work real.

Review the route, safe browser context, and replayable API behavior that make it reusable.

Choose the running local app and target; configure separate local authentication when required.

Keep iterating without reconstructing the path to the bug every time.

When you need more control

For coding agents

Agents can already reproduce many browser bugs from a competent description. StatePort's public MCP lets an agent work from an existing reviewed State Card. With explicit permission and a capable runtime, an agent can also create a new Card through bounded Capture and mandatory Review.

Planned

One State Card can now move between developers. Shared workspaces, members, organization policies, and persistent team libraries remain future capabilities.

Team collaboration will add organization-level controls without changing the free, temporary State Card handoff.