PROVIDER GUIDE
OpenClaw
The original CTRL NODE provider. OpenClaw is a full agentic session runtime — the Bridge connects to the OpenClaw gateway, spawns sessions on demand, and manages the full task lifecycle.
Gateway token Session polling
Requirements
- ✓ An OpenClaw gateway running and accessible (self-hosted or managed)
- ✓ A gateway token (
OPENCLAW_GATEWAY_TOKEN) - ✓ The gateway URL (
OPENCLAW_GATEWAY_URL), e.g.https://gateway.example.com - ✓ CTRL NODE Bridge installed on your machine (GitHub)
Quick start
Run the Bridge
$ PAIRING_TOKEN=your-pairing-token \
OPENCLAW_GATEWAY_TOKEN=gw-token-… \
OPENCLAW_GATEWAY_URL=https://gateway.example.com \
./ctrlnode
OPENCLAW_GATEWAY_TOKEN=gw-token-… \
OPENCLAW_GATEWAY_URL=https://gateway.example.com \
./ctrlnode
.env file
PAIRING_TOKEN=your-pairing-token
OPENCLAW_GATEWAY_TOKEN=gw-token-…
OPENCLAW_GATEWAY_URL=https://gateway.example.com
Environment variables
| Variable | Required | Description |
|---|---|---|
| OPENCLAW_GATEWAY_TOKEN | Yes | Authentication token for the OpenClaw gateway. |
| OPENCLAW_GATEWAY_URL | Yes | Base URL of the OpenClaw gateway, e.g. https://gateway.example.com. |
How the Bridge dispatches to OpenClaw
When CTRL NODE dispatches a task to an OpenClaw agent:
- The Bridge authenticates with the OpenClaw gateway using the gateway token.
- It creates a new session for the task.
- Session output is polled and streamed back to CTRL NODE via the WebSocket in real time.
- On session completion or error, the task status updates in the CTRL NODE dashboard.