Skip to main content
The plugin reads configuration from channels.openclaw-simplex.

Minimal config

Single-account config

If accounts is not set, the root channels.openclaw-simplex object acts as the default account config.

Multi-account config

If accounts is set, each account entry can override the shared root config. This is the model to use when different SimpleX identities or runtimes should map to different OpenClaw channel accounts.

Field reference

A channel/account is considered configured only when connection.wsUrl, connection.wsHost, or connection.wsPort is present. If none of those are set, OpenClaw will not treat the channel as startup-ready.
SimpleX-native live replies apply only to assistant text previews and final text. Media, polls, and explicit message actions continue to use normal SimpleX sends. If a live update fails or a payload contains media, the plugin falls back to normal delivery.
draftChunk is OpenClaw’s standard live-draft chunking shape and is optional. When set, it takes precedence over streaming.minChars and streaming.wordBoundary; when unset, those legacy settings and their defaults are unchanged. It only shapes the live in-progress draft — the final reply is always delivered in full and never truncated.
mentionPatterns scopes where the agent’s name patterns count as a mention, so a bot can stay quiet in some groups and respond to name mentions in others. It refines mention handling only; groupPolicy, groupAllowFrom, and per-group requireMention still decide whether a group is handled at all.

What belongs in plugin config vs runtime startup

This plugin talks to an already running external simplex-chat process. That means the OpenClaw config only models settings the plugin can truthfully use at runtime.

Good fit for plugin config

  • connection.wsUrl, wsHost, wsPort
  • connection.allowUnsafeRemoteWs
  • connection.connectTimeoutMs, connection.commandTimeoutMs, and connection.directoryTimeoutMs
  • connection.autoAcceptFiles
  • streaming.nativeTransport, streaming.throttleMs, streaming.minChars, and streaming.wordBoundary
  • draftChunk.minChars, draftChunk.maxChars, and draftChunk.breakPreference
  • messageTtlSeconds and filePolicy
  • OpenClaw policy and UX settings such as dmPolicy, allowFrom, groupPolicy, groupAllowFrom, mentionPatterns, contextVisibility, actions, and reactionLevel

Intentionally not mirrored into plugin config

These are primarily simplex-chat startup or environment flags, so they belong in the host-managed service command line, not in channels.openclaw-simplex:
  • transport/bootstrap: —server, —xftp-server, —socks-proxy, —socks-mode, —host-mode, —required-host-mode, —smp-proxy, —smp-proxy-fallback, —smp-web-port
  • local process/file layout: -d/—database, -k/—key, —files-folder, —temp-folder, —log-file
  • runtime process behavior: —device-name, —maintenance, —mute, —mark-read, —reactions, —create-bot-display-name
Those flags can still be valuable, but the right place to set them is the supervised simplex-chat service definition described in Runtime Setup.