What supermessage is

supermessage is a Matrix client. It talks to any Matrix homeserver, and the people you message can use Element, Cinny, or anything else.

What makes it different is who else is in the room.

Agents are participants, not a panel

Most tools put an agent in a sidebar: a chat box bolted onto an app, separate from the conversation your team is actually having.

supermessage puts the agent in the room. When an agent takes a turn, asks permission, or reaches a gate that needs a human answer, that appears in the timeline, in sequence, next to what everybody else said.

Each of those is rendered as what it is:

What arrives	How it reads
`dev.agentpod.turn.v1`	Turn — what the agent did
`dev.agentpod.permission.v1`	Permission — what it wants to do, and your answer
`dev.kaambaan.gate.v1`	Approval — a card waiting on a decision

It does not stop being Matrix

This is a constraint the project holds itself to, not a side effect.

Every custom event carries a plain-text fallback body. Open the same room in Element and you see a readable sentence, not an error. Nothing about using supermessage locks a room, a homeserver, or the people in it to supermessage.

An agent’s live output arrives over to-device messages, which are deliberately temporary — not stored on the homeserver, not paginated, gone after a restart. That is the right shape for partial text being typed, and a hard ceiling: anything that should be readable tomorrow is a real message in the room instead.

One core, five platforms

   ┌───────────────────────────────────────┐
   │  UI per platform                      │
   │   ├─ desktop: Svelte in a webview     │
   │   └─ iOS: native SwiftUI over UniFFI  │
   ├───────── Tauri commands/events ───────┤
   │  Rust core (supermessage-core)        │
   │   matrix-sdk · sliding sync · E2EE    │
   └───────────────────────────────────────┘

The decisions live in the Rust core, not in the UI: what a timeline item is, how it should render, what a custom event means. A platform renders that decision rather than re-deriving it, which is why five front ends do not drift into five different products.

What it is not

It is not a harness — it does not run agents. AgentPod manages where they run, and kaambaan decides what they work on. supermessage is where you and they talk.

Concepts — rooms, spaces, and the event types above
Working with agents — the part that is not like other clients