StatePort
Download

Save the State Card. Then choose where to open it.

StatePort gives a difficult application state a named, reviewable entry point. Captured source uses eligible saved-page material; Local uses a running local app and current code.

State Card

01PrepareOpen the app in the managed browser.
02CaptureReproduce the difficult state.
03ReviewInspect evidence and exclusions.
04SaveKeep a named State Card.
05ReproduceOne launcher, your current code.

A state you can return to.

The workflow is deliberate. Each step makes the resulting context easier to understand before it becomes part of your development work. This illustration follows a first-party Manager permissions form that reaches a validation error after project export is enabled.

  1. 01

    Prepare and capture the difficult moment

    Open the application in the StatePort-managed browser, reproduce the state worth keeping, and capture the supported page, browser, form, storage, and API evidence — or rerun one supported CodeceptJS test under Capture.

  2. 02

    Review before you save

    Inspect the saved state, Recorded Journey coverage, replayable API exchanges, console evidence, and protected-value decisions before the State Card exists.

  3. 03

    Reproduce from one unified launcher

    Pick the current local target, the saved state or Journey, a Development Profile or Clean Session, and optional per-run protected-value authorization — then reproduce against current code while supporting responses stay controlled. Supported state may be reconstructed from semantic actions and checkpoints; this is not serialized React or Vue runtime memory.

  4. 04

    Clean Session check

    When the verification surface is available in your build, check the exact State Card or revision in a fresh context.

What runs when you capture and open.

StatePort Desktop provides the managed browser boundary around the local workflow. It is not a browser extension or a copy of your app's backend.

Capture and reproduction run in the StatePort managed Chromium browser boundary — not a browser extension, not a copy of your app's backend.

A State Card does not clone a repository, install dependencies, start arbitrary services, or restore a historical database. Local mode needs your app running at the selected target.

Normal Beta Capture does not require a customer Capture SDK or app-code instrumentation.

When authentication is needed, an explicit machine-local protected-value decision is separate from ordinary capture.

See current Beta scope

Coding-agent branch

Work directly or with your coding agent.

Setup works before the first Card. Once connected, public MCP supports source assistance without Capture, supported live checks, and exact saved-Card reuse. New browser cases follow the installed runtime's automatic Capture policy and permissions. Your agent changes code; StatePort provides context and verification evidence. Manual Capture and one-card sharing remain complete paths without an agent.

See the agent workflow

Reusable reproduction

01Reuseexisting Card → Use with agent → Copy task
02Capture with permissionCapture with an agent → capability and permission check → Clean Session
03Reviewconfirmed symptom → Stop → Review → Save; otherwise discard

Make the dependency boundary visible.

Keep the surrounding world stable while you choose exactly which route should use local code.

Supporting dependency
Frozen
Route under change
Local
Unexpected request
Block

A better starting point for local work.

A State Card is not a promise to recreate every system. It is a bounded, inspectable way to return to the application context you actually need.

Read the security approach