Install the SeanPropApp bridge

One command on your computer connects your Claude or ChatGPT subscription to the SeanPropApp workspace. A small open-source app bridges your paid subscription, so there is no API key and no token charges per analysis.

Security review before you run this

The package is exactly @seanpropapp/cli and the repo is github.com/seanomich/seanpropapp-cli. It is open source, so you can read exactly what the bridge does and does not do: read the source on GitHub.
npx runs code locally on your computer. The bridge listens only on localhost (127.0.0.1) and uses a one-time pair token: never share it.
Your prompts go to your chosen AI provider, not stored by SeanPropApp. SeanPropApp never sees an API key or token.
Bridge telemetry is a minimal heartbeat, off by default and visible; autostart is a separate, explicit choice.

Step 1: run this, detected Any OS

Open a terminal on your computer and paste this.

npx @seanpropapp/cli@latest connect

The command pulls down the open-source CLI and starts a local bridge. The bridge needs to be running whenever you use SeanPropApp; re-run the command to start it again.

Want a hand? Ask your own AI

Paste this into your own AI assistant (for example ChatGPT or the Claude desktop app): not SeanPropApp’s in-app chat. It asks the assistant to security-review the package first, then walk you through the install.

Do a SECURITY REVIEW first, then guide me through installing this.
Package: @seanpropapp/cli   Repo: github.com/seanomich/seanpropapp-cli
It runs via npx (local code execution), bridges on localhost with a
one-time pair token; prompts go to my own AI provider, not stored by
SeanPropApp; telemetry is a minimal heartbeat, off by default; autostart
is a separate, explicit choice.
Verify the package + repo, flag anything risky, then walk me through
"npx @seanpropapp/cli@latest connect" and troubleshoot my setup.
Guide: seanpropapp.com/install

What this does

The bridge process listens on 127.0.0.1:17492 for requests from the SeanPropApp browser tab, validates a one-time pair token, and forwards each request to your existing Claude CLI or Codex CLI subscription.

Nothing leaves your machine except the prompts your subscription would already see. Your API tokens stay yours; SeanPropApp never sees a key.

How the CLI Bridge uses your subscription

The CLI Bridge runs your own Claude or Codex CLI on your machine, on your existing AI subscription. Your prompts never pass through a SeanPropApp server, and no per-token API charges apply.

This path depends on your AI vendor's terms, and those can change. A vendor may decide their subscription plans can only be used inside their own apps, which would mean CLI Bridge users need to switch to an API key. If that happens we will tell you plainly. Switching is quick: SeanPropApp fully supports API keys (you pay your vendor per token instead), and your saved work is unaffected either way.

Diagnose and keep it current

If a run fails or the bridge will not connect, run the built-in self-check. It reports your Node version, whether the bridge is reachable, your current CLI version, and whether a newer one is available.

npx @seanpropapp/cli doctor

Stay on the latest. The bridge is a long-lived background process, so a version you paired weeks ago can be behind on fixes (streaming, model names, connection handling). We recommend always running the latest:

npx @seanpropapp/cli@latest connect

Default to the latest. The only reason to pin a specific version is reproducibility (for example after a bad release), and that is rare; if you pin, you own keeping it current.

Common challenges

Bridge not running: The bridge only runs while the command is active. Re-run npx @seanpropapp/cli@latest connect to start it, then reload the workspace.
Browser permission prompt: Your browser asks permission for SeanPropApp to reach the local bridge (the local network / “access other apps and services on this device” prompt). This is expected and only for the bridge: allow it. See the OS-permission links below.
Safari / WebKit: Some WebKit browsers cannot complete pairing yet. Use Chrome, Edge, or Firefox for the bridge, or add an API key instead.
Token mismatch or wrong port: Re-pair to issue a fresh token. Run npx @seanpropapp/cli doctor to confirm the port the bridge is listening on.
Behind the latest version: Run npx @seanpropapp/cli@latest connect to refresh to the newest CLI, then re-pair.

OS and local-network permissions

The browser’s local-network prompt is the Private Network Access check. Allow it only for SeanPropApp reaching the local bridge; you never need to grant broad system access. Reputable references:

Grant only what the bridge needs (local-network access for SeanPropApp). Do not disable your firewall or grant blanket permissions.

The bridge is open source

@seanpropapp/cli is open source at github.com/seanomich/seanpropapp-cli. You can read every line of what the bridge does, build it yourself, and verify it never sends your prompts or keys anywhere except your chosen provider.

Already installed?

If you’ve already installed @seanpropapp/cli and just need a fresh pair link, run npx @seanpropapp/cli pair instead, then open the URL it prints.

Open pair page

Bridge command not found after install? Fix your PATH

`npm install -g` puts binaries in a folder that may not be on your shell’s PATH. Pick the snippet for your OS, paste it into a terminal, then re-run npx @seanpropapp/cli@latest connect.

If you installed globally, keep it current. A global install shadows npx: once npm install -g has put a copy on your PATH, running the connect command WITHOUT the @latest tag keeps running THAT copy and never picks up new releases, however many ship. Either always use the @latest form above, or remove the global copy with npm uninstall -g @seanpropapp/cli and let npx fetch the current version each time.

macOS (zsh, default)

# Find where npm puts global binaries:
echo "export PATH=\"$(npm config get prefix)/bin:$PATH\"" >> ~/.zshrc
source ~/.zshrc

# Verify:
which seanpropapp

macOS (bash)

echo "export PATH=\"$(npm config get prefix)/bin:$PATH\"" >> ~/.bash_profile
source ~/.bash_profile

Linux (bash / zsh)

# Use whichever shell config your distro uses (.bashrc or .zshrc):
echo "export PATH=\"$(npm config get prefix)/bin:$PATH\"" >> ~/.bashrc
source ~/.bashrc

Windows (PowerShell)

# Add npm's global prefix to your PATH (run once, then restart PowerShell):
$npmPrefix = npm config get prefix
[Environment]::SetEnvironmentVariable("Path", "$env:Path;$npmPrefix", "User")

Prefer an API key instead? Add an API key in Settings

This guide lives at seanpropapp.com/install.