Skip to main content
Install the open-source Bridge binary (ctrlnode) from github.com/ctrlnode-ai/ctrlnode, pair it with CtrlNode, and confirm the app shows connected.

​
Before you start

  • A CtrlNode account at app.ctrlnode.ai
  • A pairing token from System → Bridge Setup or the setup wizard Token step
  • Network egress to wss://api.ctrlnode.ai (default control plane)

​
One-line installers

The script:
  • Downloads the latest ctrlnode.exe from GitHub Releases
  • Installs to %LOCALAPPDATA%\Programs\ctrlnode (or a path you choose)
  • Adds that folder to your user PATH (command name: ctrlnode)
  • Sets BASE_PATH to your chosen workspace parent (where {BASE_PATH}/.ctrlnode lives)
  • Optionally starts the Bridge when you answer y at the end

​
Manual download

Download from GitHub Releases. On Linux:
avx2 → standard binary; otherwise use -baseline.

​
Start the Bridge

Copy the pairing token when generated — you cannot view it again. Regenerate from Bridge Setup if you lose it.
Installers also write ~/.ctrlnode/.env with PAIRING_TOKEN, SAAS_URL, and BASE_PATH when you use the interactive flow.

​
Token and BASE_PATH precedence

If pairing fails after a new token, unset stale shell variables:

​
Verify in CtrlNode

  1. Open System → Bridge Setup — status Connected (green).
  2. Open Team — agents appear after sync_*_agents on connect.
  3. Dispatch a test task — moves to In progress with live activity.

​
Run as a service (optional)

Run ctrlnode as a long-lived process under the same user that owns BASE_PATH and ~/.ctrlnode/.env (systemd, Windows Task Scheduler, or a supervisor).

​
Next steps