Matrix bot reference
Bot commands are accepted only in a verified private channel with exactly the sender and the Cumments bot. A command elsewhere is consumed silently so it is never projected as a comment. Sensitive tokens are printed only in that private channel.
The private channel for Bot commands and cumments-claim:... tokens must be
unencrypted — the Bot currently does not decrypt m.room.encrypted and
therefore cannot read !cumments ... or claim tokens in an encrypted room
(it will join but appear unresponsive). If the homeserver or client creates
E2EE DMs by default (notably Tuwunel
encryption_enabled_by_default_for_room_type = "invite"), create the DM with
encryption disabled, re-invite the bot and resend the command. This is a
Bot-command limitation, not a Matrix rule; comment rooms may be encrypted or
not, and site owners may be on a different homeserver (federated) — only the
Bot DM for commands must be unencrypted.
Commands use <domain> <resource> <verb> syntax. Commands marked confirm
must be repeated with --confirm; the first invocation returns the exact
confirmation command.
Site lifecycle and status
Roles
Role claims are activated by the target user sending
cumments-claim:<verify_token> to the bot.
Admin add/remove and ownership-transfer bot commands are deliberately absent. Site-owner bootstrap is the trust boundary for those capabilities, preventing a chat actor from rewriting ownership or the admin roster.
Pages and stickers
Operator operations
backfill requires a running worker in the same process. If no queue is wired,
the bot reports that it is unavailable rather than silently doing nothing.