Matrix Setup

Connect OpenClaw to Matrix (Element, Synapse, etc.)

Extension-based channel. Matrix support is provided via the OpenClaw Matrix extension. For a general channel setup walkthrough, see Channel Setup Tutorial.

OpenClaw connects to Matrix—the decentralized, open protocol used by Element and many self-hosted homeservers—via the Matrix extension. Your assistant can handle DMs and participate in rooms. Ideal for privacy-focused teams or anyone using Element, Synapse, Dendrite, or other Matrix-compatible servers.

Requirements: The Matrix extension installed and configured, a Matrix account (or bot user), and a homeserver URL. Setup follows the same patterns as other extension-based channels.

Quick Setup

  1. Install the OpenClaw Matrix extension (see extension docs)
  2. Configure homeserver URL and bot/user credentials
  3. Enable the Matrix channel in OpenClaw config
  4. Invite the bot to rooms or start a DM

For authoritative steps and config schema, see docs.openclaw.ai/channels and the Matrix extension repository.

Why Matrix

  • Decentralized — No single provider; federated servers
  • Self-hostable — Run your own homeserver (Synapse, Dendrite) alongside OpenClaw
  • E2E encryption — Supported in Matrix rooms and DMs
  • Interoperable — Bridge to other protocols (IRC, Telegram, etc.)

Supported Features

  • Text messages
  • Media and files
  • DMs and rooms
  • Reactions and threads (where supported by client)

Pairing and rooms

Matrix rooms can be public. Restrict who can trigger the bot with pairing and room allowlists in config. For E2E rooms, confirm the extension supports your encryption setup—broken crypto often shows up as “bot never receives.”

E2EE rooms

Encrypted Matrix rooms need supported crypto on the bridge host. If the bot never sees events, verify keys and room membership before blaming OpenClaw config.

Related