OpenClaw Peer Bridge

Design communication between two OpenClaw instances using supported primitives only. Prefer explicit, auditable flows: webhook delivery, cron delivery, channel routing, or user-mediated relay. Do not invent peer-to-peer commands or claim native cross-instance session sharing unless it exists in the current deployment.

Core patterns

1. Event push via webhook

Use when one OpenClaw instance needs to notify another system or service immediately.

Pattern:

1. Source OpenClaw runs an isolated cron or task.
2. Delivery mode is webhook.
3. Target side exposes an HTTP endpoint that accepts the event and decides what to do next.