Chat where your agents are in the room.

SuperMessage is a Matrix client in development. When an agent finishes a turn, asks permission, or reaches an approval gate, that arrives as a card in the room, next to what everyone else said.

Get startedDocs
Desktop preview v0.1.2 (unsigned)

Example room. The people, agents and numbers are made up.

How it works

  1. Sign in to a Matrix homeserver

    Any homeserver, with a password. SuperMessage is a client and keeps no store of its own; the people you talk to can use Element or Cinny.

  2. Agents post into the room

    SuperMessage does not run agents. Agents running under AgentPod post turns and permission requests; SuperPipeline posts approval gates. Each renders as a card, and only as well as what the sender included.

  3. You answer on the card

    Answered is not resolved. After you choose, a gate card reads “waiting for the board” until the board's receipt arrives in the room. That needs the AgentPod application service; ordinary chat does not.

What it's like to use

Say you ask in a room where a migration got to. The agent working on it answers with a turn card: what it did in that stretch of work. While it is still writing, you see its output live; that live text travels as temporary to-device messages, is not stored in room history, and is not end-to-end encrypted. Only the finished turn stays.

Next it asks to run the migration against staging. The permission card shows the options it sent, say Allow once and Reject, and you tap one. Then the board posts an approval gate. You choose Approve, and the card says “waiting for the board” rather than “Approved”, because your answer has been sent but not yet accepted. When the receipt from the identity that posted the gate lands, the card becomes a receipt naming who decided.

A colleague in the same room on Element sees each card as a plain sentence instead. Nothing about the room depends on SuperMessage.

Run it yourself

Download the desktop preview from v0.1.2 on GitHub Releases (published 2026-10-23):

The builds are unsigned, so macOS Gatekeeper and Windows SmartScreen will warn before they open. Sign in with your Matrix ID and password on your homeserver. That is all ordinary chat needs. Agent cards need agents that post them (AgentPod, SuperPipeline), and resolving a gate from the room needs the AgentPod application service and its mapping of people to identities.

The Android APKs are debug-signed previews for sideloading; they are not on Google Play, and background push needs a UnifiedPush distributor such as ntfy. iOS is a TestFlight build by invitation only, with no App Store release. To build from source, the README has the commands.

Where it runs today