Most agent chat channels in OpenClaw assume a platform bot identity: a bot username, a phone number, an app registration, or some other platform-managed endpoint. Within OpenClaw’s channel ecosystem, this plugin enables a communication model that does not rely on platform identity or bot registration. With SimpleX, the invite or address link becomes the access boundary: generate it, share it intentionally, revoke it when needed, and the agent does not expose a platform-discoverable bot identity. The implementation keeps developer-facing boundaries explicit: OpenClaw enforces policy, the plugin translates channel events and actions, and a separately managedDocumentation Index
Fetch the complete documentation index at: https://openclaw-simplex.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
simplex-chat runtime handles the SimpleX WebSocket API.
Getting Started
Install the runtime and plugin, configure
wsUrl, generate the first invite, and verify end-to-end messaging.Runtime Setup
Run
simplex-chat yourself, wire OpenClaw to its WebSocket endpoint, and optionally move it under systemd or launchd.Why SimpleX
See why this channel is built around invitation-based reachability, self-hostable relays, and no platform account dependency.
How It Works
Learn how routing, pairing, policy checks, and outbound delivery fit together.
Migration
Upgrade existing
simplex installs to openclaw-simplex and preserve pairing state.Troubleshooting
Diagnose startup, runtime, invite, and policy issues quickly.