Install the open-source Bridge binary from github.com/ctrlnode-ai/ctrlnode, pair it with CtrlNode, and confirm the app shows connected.Documentation Index
Fetch the complete documentation index at: https://docs.ctrlnode.ai/llms.txt
Use this file to discover all available pages before exploring further.
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
- Windows (PowerShell)
- Linux / macOS
- Downloads the latest
ctrlnode-bridge.exefrom GitHub Releases - Installs to
%LOCALAPPDATA%\Programs\ctrlnode(or a path you choose) - Adds the folder to your user PATH
- Sets
AGENTS_FOLDERto your profile directory (workspace parent) - Optionally starts the Bridge when you answer y at the end
Manual download
| Platform | Asset |
|---|---|
| Linux x64 (AVX2) | ctrlnode-bridge-linux-x64 |
| Linux x64 (older CPUs / many cloud VMs) | ctrlnode-bridge-linux-x64-baseline |
| macOS Apple Silicon | ctrlnode-bridge-darwin-arm64 |
| Windows x64 | ctrlnode-bridge.exe |
avx2 → standard binary; otherwise use -baseline.
Pairing token
- Windows
- Linux / macOS
ctrlnode-bridge with no env vars and complete the interactive wizard — it writes ~/.ctrlnode/.env.
Token precedence
| Source | Wins? |
|---|---|
Variable already in shell ($env:PAIRING_TOKEN / export PAIRING_TOKEN) | Yes — overrides file |
~/.ctrlnode/.env | Used when shell is unset |
| Wizard prompt | Used on first interactive run |
Verify in CtrlNode
- Open System → Bridge Setup — status should show Connected (green).
- Complete Team or setup Agent — agents should appear when registered.
- Dispatch a test task — it should move to In progress and stream activity.
Run as a service (optional)
The Bridge is a single long-lived process. Use your platform’s service manager (systemd, Windows Task Scheduler, or a process supervisor) to restart on boot. Point the service at the same user account that owns AGENTS_FOLDER and ~/.ctrlnode/.env.
Next steps
- Bridge configuration —
PROVIDERS, API keys, timeouts - Providers — install Copilot, Claude, Cursor, etc.
- Bridge overview — architecture and routing