Install StatePort

Install StatePort

Download StatePort from stateport.dev/download.

The download page is the source of truth for current Public Beta platform and architecture availability. A platform is available only when the page shows a real versioned installer for it. If your platform is marked unavailable, there is no supported public installer for that target yet.

Install the Public Beta

1. Open stateport.dev/download.
2. Choose the installer for your exact operating system and architecture.
3. Check the displayed version and integrity information when provided.
4. Install and open StatePort through the normal operating-system flow.
5. Launch StatePort and continue in Free Capture.
6. Continue to Capture your first State Card.

Do not use an installer for another architecture merely because it is visible. Unsupported or unproved targets remain intentionally unavailable.

For every platform advertised as supported, the published installer and its release notes are the complete installation contract. StatePort does not require development tooling as part of the public installation experience.

The Windows x64 beta is unsigned: it has no Authenticode signature or verified publisher. Microsoft Defender SmartScreen may warn, and Windows in S mode or organization policy may block installation. Read the Windows limitations before downloading. Capture on Windows uses StatePort’s managed browser; the ordinary Chrome Capture extension is unavailable there.

When opening a local Ubuntu .deb, a software center may show the package name stateport, a generic icon, and no screenshot gallery. The package includes StatePort’s metadata and original icon; after installation, use the StatePort entry in your application launcher.

Update checks

StatePort may check for a newer Public Beta in the background. This check is best-effort: no prior check, an expired result, unavailable network, timeout, invalid response, or local update-check storage problem does not disable otherwise-authorized work. You can keep using Free Capture, Developer access, CLI, or MCP according to your normal access tier while an update check cannot complete.

An ordinary newer-version notice is non-modal and does not interrupt current work. Only a previously received, strictly validated decision that this exact build is retired or revoked enters the limited recovery mode; your Library, State Card inspection, local Export, Settings, and diagnostics remain available there.

Older saved run evidence can contain BETA_POLICY_VERIFICATION_REQUIRED. It is a historical compatibility reason, not a current update-check requirement or a reason to block a new authorized operation.

Browser sessions

StatePort uses its own managed browser sessions:

• Development Profile — a persistent StatePort-owned browser profile for everyday work. It may keep supported browser settings, extensions, and browser-managed local login state between runs.
• Clean Session — a fresh isolated browser context for runs that should not depend on Development Profile state.

Reproduction runs in these managed sessions. The separate Chrome Capture extension can record the tab you select in your ordinary Chrome. It does not copy or reset that browser profile, and coding agents cannot control that tab through StatePort.

A platform is not advertised as supported until its packaged browser path has passed the corresponding release checks. Follow the installer and release notes for the browser/runtime requirements of the exact release you download.

Access after installation

StatePort starts in permanent Free Capture.

Within the supported Public Beta scope, Free Capture includes:

Capture
→ Review
→ Save and manage State Cards
→ Share one State Card

Receive
→ Import
→ Inspect shared State Cards

Free Capture requires no StatePort account, Paddle purchase, payment card, or Developer entitlement and has no arbitrary State Card, project, or monthly-capture quota.

Developer trial

Working from a saved State Card against current code is Developer functionality. This includes reproduction, Journey execution, supported response experiments, revisions, comparisons, and execution-capable CLI/MCP operations.

You can explicitly start one full 14-day Developer trial without a payment card when you choose a Developer operation. Enter an email address and verify the bounded code we send before the trial begins. That email is used only for one-time trial eligibility and recovery; it is not marketing consent, and no password or StatePort account is required.

Trial time does not start on:

• download or installation;
• first launch;
• Capture, Review, or Save;
• Library browsing;
• Share or Import;
• viewing pricing or documentation.

Entering an email or requesting a code also does not start trial time. If a code expires or cannot be verified, request a new one or change the email; Free Capture remains available throughout.

When the trial ends, local State Cards remain available and Free Capture continues to work. Developer execution becomes available again after Developer access is restored.

Paid activation

After a verified Monthly or Founding purchase, the approved website/Paddle flow hands activation to StatePort Desktop.

The app may use the stateport:// deep link or the documented manual fallback. Existing bounded scenariodeck:// activation links remain accepted for compatibility. Activation grants are bounded and one-use. Do not paste activation or recovery codes into public issues, chat, analytics, screenshots, or logs.

CLI and MCP

On Ubuntu, installing the .deb adds stateport to the command line.

On Windows, the installer adds the bundled CLI to your user PATH. Open a new terminal after installation, then run stateport --help.

On macOS:

1. Move StatePort.app from the .dmg to /Applications.
2. Open StatePort once. The app tries to make the stateport command available for your user in the default zsh shell, without an administrator password or manual shell configuration.
3. Open a new terminal and check the command:

stateport --help

If the command is not available in a new terminal, you can keep using Desktop normally. Automatic setup does not interrupt startup with a warning or request administrator access. StatePort preserves existing commands and shell settings, records a setup diagnostic, and retries on the next app launch. You can use the bundled launcher directly:

/Applications/StatePort.app/Contents/Resources/stateport-cli --help

Run stateport --help to see commands and stateport state list to list State Cards in the current project’s .scenariodeck directory. The installed CLI uses the bundled runtime and needs no separate development tooling. See the CLI reference for command details.

Desktop, CLI, and MCP use the same operation-based access policy:

• approved capture/import/inspection operations remain available through Free Capture;
• Developer access is required before a saved reproduction is executed or changed through CLI/MCP;
• a renderer or agent cannot promote Free/Expired access to Developer by supplying a client-side flag.

Release information

Use the download page and the release notes linked from it for the exact version, available platforms, architecture, integrity information, signing/notarization status where applicable, and current known limitations.