simplex ids. For a fresh install, start with Getting Started.
What changed in 1.0.0
- plugin id:
simplex->openclaw-simplex - channel id:
simplex->openclaw-simplex - pairing approval commands now use
openclaw-simplex
Gateway method names keep the
simplex.* prefix. Programmatic invite flows still use simplex.invite.create, simplex.invite.list, and simplex.invite.revoke; newer runtime, request, group, and link-onboarding methods use the same prefix.connection and removing unsupported managed-mode fields.
1
Start the external SimpleX runtime
Run Make sure your config points to that endpoint under
simplex-chat yourself and expose the WebSocket endpoint the channel should use:channels.openclaw-simplex.connection.wsUrl.2
Preview the migration
3
Apply the migration
simplex config keys, normalizes legacy runtime fields for the external WebSocket runtime, and renames the related pairing/allowlist state files in the OpenClaw state directory.4
Verify the new ids and pairing flow
Check the plugin under its new id:If you need to re-add the channel explicitly, use the new channel id:Pairing approval also uses the new channel id:Send a SimpleX message from an already approved contact and confirm the approval still holds after migration.
Target config shape
After migration, the channel should be configured underopenclaw-simplex:
What the migration helper updates
plugins.entries.simplex->plugins.entries.openclaw-simplexplugins.installs.simplex->plugins.installs.openclaw-simplexplugins.allow/plugins.denychannels.simplex->channels.openclaw-simplex- legacy top-level runtime fields such as
wsUrl,url,host, andportare moved underconnection - unsupported managed-mode fields such as
managed,cliPath,token, anddbFilePrefixare removed from root and per-account SimpleX config - OpenClaw pairing and allowlist state files under the OpenClaw state directory