StatePort

Capture the setup once. Reopen it against current code.

StatePort records the supported browser and API conditions behind a useful web-app setup or bug, saves them as a State Card, and lets you return to the same reproduction without rebuilding it every time.

Get started · Read the CLI reference

StatePort is currently distributed as a Public Beta. Use stateport.dev/download for the exact platforms and architectures available in the current release.

The current workflow

Capture Session
→ Review / redact / curate
→ Save State Card
→ Reproduce Saved state or Recorded Journey
→ change current code or one supported response
→ save revision
→ reproduce / compare

A current State Card points to a bounded Capture Session containing safe semantic actions and meaningful checkpoints plus immutable State Capsule material for supported browser/API replay.

Send the reproduction

One supported State Card can be shared through a temporary encrypted link:

sender shares State Card
→ recipient imports it locally
→ recipient reproduces it against their own current code

No StatePort account or Developer license is required merely to send, receive, import, or inspect one card. Ordinary Card-only links and files exclude protected values, browser-profile data, local Auth Bindings, and local sign-in state. Desktop Share and Export can separately include explicitly selected protected values or a Protected Persona, which the recipient must review and accept. Anyone with an exported file can access its included data; a delivered file cannot be revoked. Developer access becomes relevant when the recipient chooses to execute the saved reproduction against current code.

This is one-card handoff, not a Team workspace or cloud-hosted execution environment.

What StatePort supports today

• bounded semantic Capture Sessions with checkpoints;
• manual Capture in the managed browser, selected-tab Chrome Capture, and the current direct CodeceptJS Run & Capture path;
• mandatory Review before a State Card is saved;
• Saved state and full/partial Recorded Journey reproduction against an explicit loopback target;
• Development Profile or Clean Session as the browser-session choice;
• DevTools in the interactive developer workflow;
• fail-closed captured-response replay with explicit loopback Local routing for supported dependencies;
• browser console/page-error evidence under the selected evidence policy;
• bounded redacted JSON response editing with immutable revisions;
• reopen and safe run comparison;
• machine-local Auth Personas/Bindings separate from portable artifacts;
• explicit protected local-value retention with per-run consent where supported;
• encrypted temporary State Card sharing, plus offline State Card file export/import;
• CLI and MCP over the same trusted runtime and access policy.

Read supported Public Beta scope before using StatePort with a new app.

Coding agents can use an existing Card through MCP. The separate agent plugins and debugging skill are a development preview. The founder reports repeated successful tests on Linux and macOS, from installation and agent connection through Card capture, a code change, reopening the same Card and comparing the result. Public host/version-bound evidence and independent provider compatibility checks remain pending.

What StatePort does not do

StatePort does not copy a backend database/server environment or browser profile, silently retain or transfer sensitive values, provide generic session replay/observability, or claim automatic root cause/fixes. Chrome Capture observes only the selected tab after your explicit Start; reproduction runs in StatePort’s managed browser.

Arbitrary third-party surfaces, anti-bot protected sites, broad streaming/media protocols, and direct test-runner integrations beyond the current supported CodeceptJS path have additional Public Beta limitations described in supported scope.

Access

Free Capture
Capture → Review → Save/manage → Share
Receive → Import → Inspect

Developer trial / paid Developer
Reproduce → Experiment → Revision → Compare

Free Capture has no arbitrary card/project/monthly-capture quota and does not consume the 14-day Developer trial. The trial starts only after an explicit Developer operation and successful email-ownership verification; no payment card, password, or account is required.

Release availability

A platform is part of the Public Beta only when the download page shows a real versioned installer that passed its release checks. An unavailable platform is intentionally not offered as a public installation target.