openclaw-agent-bridge

Cross-agent messaging to OpenClaw is done by bridging external agents through a Protocol v3 WebSocket gateway. The bridge enables tools like Hermes, Claude Code, cron jobs, webhooks, and CI/CD workflows to dispatch chat.send RPC messages to target OpenClaw sessions.

WebSocket cross-agent messaging requires secure, device-signed authentication using an Ed25519 keypair. You must obtain a paired device token through a pairing workflow and store the keypair in a designated local directory before dispatching messages.

Device pairing with the OpenClaw gateway is performed using the pair.py script. Running this script obtains and stores the necessary device token, allowing your external agent to authenticate and send messages via the WebSocket bridge.

Yes, the OpenClaw bridge supports connecting CI/CD workflows, cron jobs, webhooks, Hermes, and Claude Code to OpenClaw agents. It routes messages from these automation pipelines across a single host or distributed environments using the WebSocket gateway.

Running the OpenClaw cross-agent bridge requires Python dependencies including the cryptography and websocket-client packages. You also need a local OpenClaw gateway, an Ed25519 keypair, and a paired device token stored in your bridge directory.

OpenClaw bridge message dispatch can fail if the local gateway is unreachable, the Ed25519 keypair is missing from the bridge directory, or the device token was not obtained through pair.py. Ensure all Python dependencies and pairing prerequisites are met.