vibe-bridge

OpenClaw channel plugin that bridges OpenClaw agents to the vibe-bridge WebSocket relay.

This is a two-way channel — inbound frames from the bridge become OpenClaw direct DMs, and the agent's reply is sent back over the same WebSocket with reply_to set to the inbound frame id.

Configuration

Add the following to your OpenClaw config (openclaw.json):

{
  "channels": {
    "vibe-bridge": {
      "pat": "your-vibe-pat",
      "event_type": "memo",
      "bridge_url": "wss://bridge.vibe.us",
      "reconnect_ms": 2000,
      "enabled": true
    }
  }
}

Or via the CLI (the wizard maps --token/--audience/--base-url onto pat/event_type/bridge_url; backend and reconnect_ms need a manual edit to openclaw.json):

openclaw channels add --channel vibe-bridge --token "<pat>" --audience "<event-type>"

Wire format

Inbound frames (bridge → plugin):

{
  "id": "<frame-id>",
  "ts": 1730000000000,
  "content": { "text": "<message>" },
  "meta": { "user_id": "<sender>", "event_type": "memo" }
}

Outbound frames (plugin → bridge), emitted when the agent replies:

{
  "id": "<fresh-uuid>",
  "ts": 1730000000123,
  "reply_to": "<inbound frame id>",
  "content": { "text": "<reply>" }
}

How it works

1. On startup, the plugin opens a WebSocket to ${bridge_url}/channels/subscribe?event_type=${event_type} with Authorization: Bearer ${pat} (and x-vibe-backend: ${backend} when set).
2. Each inbound JSON frame is dispatched into OpenClaw as a direct DM via dispatchInboundDirectDmWithRuntime. meta.user_id becomes senderId; the rest of meta is flattened (string-coerced) into extraContext.
3. When the OpenClaw agent replies, the plugin emits an outbound frame with reply_to set to the inbound frame.id back over the same socket.
4. On socket close, the plugin reconnects after reconnect_ms until aborted.
5. Handshake failures (e.g. 401 from a bad PAT) surface via the unexpected-response event with the HTTP status; the plugin keeps retrying.