Run the bridge on your machine

You need at least one AI CLI installed, signed in, and validated on this machine. The bridge launches the official CLI as a subprocess and streams its output back. It never sees your login, and if a detected CLI fails validation Synchronex falls back to Synchronex cloud.

Install Node 20 first, then copy the vendor setup for the CLI you want Synchronex to use locally. Once the bridge is running (see Install below), run npx @synchronex/agent-bridge@latest status to confirm the provider is validated.

# macOS
brew install node

# Windows PowerShell
winget install OpenJS.NodeJS.LTS

# Ubuntu / Debian
curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -
sudo apt-get install -y nodejs

# macOS / Linux / WSL
curl -fsSL https://claude.ai/install.sh | bash
claude

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex
claude

# Validate
claude -p "Reply with exactly: ok" --output-format text

# macOS / Linux
curl -fsSL https://chatgpt.com/codex/install.sh | sh
codex

# Windows / npm fallback
npm install -g @openai/codex
codex

# Validate
codex exec --json "Reply with exactly: ok"

npm install -g @google/gemini-cli
gemini

# Validate
gemini -p "Reply with exactly: ok" --output-format json

agent --version
agent --print --output-format text "Reply with exactly: ok"

Pick whichever fits how you work — all three run the same bridge.

npx @synchronex/agent-bridge@latest

curl -fsSL https://synchronex.ai/bridge/install.sh | sh

irm https://synchronex.ai/bridge/install.ps1 | iex

npx is quickest to try. For a bridge you want running all the time, the install script or binary gives you a real installed command — better than an ephemeral npx process for a long-running daemon.

The first run walks you through a device-code authorization: it prints a code, opens your browser, and you approve the device while signed in to Synchronex. The bridge then stays online and listens for work.

# Installed via the one-line script or binary:
synchronex-agent-bridge

# Or with npx:
npx @synchronex/agent-bridge@latest

One bridge can serve several Synchronex accounts from the same machine — for example your primary account for daily work plus a separate test or client account. Each account is paired independently and runs its own session authenticated with its own token, so work is only ever routed to the account that owns it. Accounts stay fully isolated.

# Sign in to the SECOND account in your browser, then on the same machine:
synchronex-agent-bridge add

# Re-run so the bridge picks up the newly paired account:
synchronex-agent-bridge

# See every account paired on this machine:
synchronex-agent-bridge status

Installed via npm install -g @synchronex/agent-bridge? Use agent-bridge instead. With npx, prefix each command: npx @synchronex/agent-bridge@latest add.

Commands above assume the one-line script or binary install. Installed via npm install -g @synchronex/agent-bridge? Use agent-bridge instead. With npx, prefix any subcommand: npx @synchronex/agent-bridge@latest add.

The bridge checks for a newer version each time it starts and prints a notice if one is available. With npx you always get the latest by running npx @synchronex/agent-bridge@latest. If you installed via the one-line script or a direct binary download, synchronex-agent-bridge update downloads and verifies the new binary's checksum before swapping it in. This only works for the standalone binary. Installed via npm install -g @synchronex/agent-bridge? Update with npm install -g @synchronex/agent-bridge@latest instead.

The curl … | sh convenience comes with a supply-chain surface, so the scripts are hardened:

• Downloads happen over HTTPS/TLS 1.2 only, pinned to Synchronex's own R2 bucket — no arbitrary hosts or redirects.
• Every binary is verified against a published SHA-256 checksum before it can run; a mismatch aborts and installs nothing. After verification, the installer runs it only to pair your account and register auto-start. Set SYNCHRONEX_NO_START=1 before piping the script to skip both steps.
• Installs into a user directory (~/.local/bin) — never with sudo or elevation.
• The scripts are open and inspectable — read them before you run them.

Inspect the exact scripts: install.sh · install.ps1. Prefer no piped shell at all? Download the binary directly from the list above, or use npx.