StatePort

Stop rebuilding state. Start where the bug is.

Reproducible application-state infrastructure for web developers and coding agents.

stateport.dev

StatePort helps you keep a difficult web-app setup available throughout development. Capture supported application state once, review it, and save it as a State Card. Open that Card later against your running local app and current code, then reuse the same setup as you debug and change behavior.

Capture → Review → Save → Open on current code → Change → Reopen → Compare

• Exact setup, reused: A State Card keeps the supported, reviewed state you chose to save so the next debugging attempt starts from the same setup.
• Current-code debugging: Open a Card against the app running locally now, not an old code snapshot.
• Replay with boundaries: Deterministic replay and fail-closed behavior are product principles; missing or unsupported dependencies should be visible, not silently replaced with live production traffic.
• Agent-facing tools: The StatePort runtime/MCP gives coding agents a structured way to work with saved state. Skills and plugins are an evolving integration layer, not a built-in autonomous debugger.

Your agent reproduces the bug once. StatePort makes that reproduction reusable.

The intended agent workflow reuses the same reviewed State Card while current code changes. The agent skills and provider integration sources are development/beta material; there is no supported plugin release or verified end-to-end agent workflow yet.

Portable state, not portable secrets. Captured material should be reviewed and redacted before it is saved or shared. Frozen/replay should fail closed rather than silently fall back to endpoints captured from production. These are boundaries for the workflow, not a promise that every web app or bug can be reproduced.