Skip to main content
Most OpenClaw channels start from a registered platform identity: a bot username, a phone number, or an application account that lives inside someone else’s platform. This plugin takes a different shape. With SimpleX, the agent becomes reachable when you hand someone a link. There is no phone-number binding and no hosted bot account to provision before the first conversation starts. That makes the channel especially useful for OpenClaw deployments where privacy, local control, and explicit network boundaries matter. The point is not that this channel replaces every platform-backed integration. It adds a different reachability and trust model to OpenClaw’s channel set.

Invitation-first reachability

Create a one-time connect link or an address link, share it only with intended users, and revoke it when that access should disappear.

No platform account dependency

No phone number, no bot username, and no bot registration step before your OpenClaw agent can receive a message.

Operator-controlled runtime

Run simplex-chat yourself, choose where the runtime and relay path live, and keep OpenClaw policy enforcement local.

OpenClaw-native operations

Pairing approval, exec approvals, allowlists, invite helpers, media support, reactions, polls, and channel status all exist in the plugin, not in ad hoc glue code.

​
What the plugin provides

A SimpleX channel backed by a local simplex-chat WebSocket runtime:
  • send/receive (text and media)
  • pairing with allowlist enforcement and same-chat exec approvals
  • shared message actions, including upload-file, reactions, polls, edits, deletes, and group actions
  • plugin tools for invite generation/list/revoke and group administration
  • one-time invite link, SimpleX address, group-link, and QR generation
  • optional SimpleX-native live assistant text replies
  • runtime status, runtime doctor, runtime user visibility, contact verification, contact-request review, group-link lifecycle, moderation, file controls, link onboarding, and heartbeat readiness support
  • Control UI configuration

​
Why teams choose it

  • They want invite-based access instead of a public bot identity.
  • They want tighter control over where the runtime and relay path live.
  • They want OpenClaw-native policy controls (allowFrom, dmPolicy, group policy) to remain the enforcement point.
  • They want to avoid coupling the agent to a hosted bot API or a phone-number-backed account.

​
Why this plugin matters

Without this plugin, using SimpleX with OpenClaw usually means custom integration work around event parsing, outbound command translation, pairing state, and invite management. This package turns that into a standard channel implementation. The contribution is not just “another channel”. It adds a channel model that is structurally different from bot-account integrations:
  • no phone number requirement
  • no hosted bot account or bot API dependency
  • access starts from a one-time invite link or reusable SimpleX address, not a public platform identity
Low risk to existing OpenClaw channels: the implementation stays isolated and is only active when openclaw-simplex is configured and enabled.