One of the easiest ways to misread Hermes is to treat messaging as one generic capability. The current research pack points in the opposite direction: Hermes messaging is a surface-by-surface rollout problem.
Discord
- DMs respond to every message
- server channels are mention-gated by default unless configured otherwise
Telegram
- privacy mode matters for group use
require_mentionbehavior must match the intended interaction pattern
Slack
chat:writeapp_mentions:readchannels:historychannels:read
Hermes documents WhatsApp through the built-in Baileys bridge path with hermes whatsapp, which is not the same as the official WhatsApp Business API model.
Practical failure checks
- expecting Discord server channels to behave like DMs
- treating Telegram privacy or mention settings as runtime failure
- assuming Slack partial behavior means the runtime is broken before scopes are audited
- adding multiple messaging surfaces before the first one is stable