Messaging Gateway
بوابة قنوات التواصل
Start with meaning, then move to detail.
This lesson explains Messaging Gateway as part of Hermes internals and extension points. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Platform Comparison, Architecture, Intentional Silence Tokens, then verify failure modes and version compatibility.
Know Python, Git, and basic project structure before changing code.
A clear outcome before you read.
- Understand Messaging Gateway without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Gateway
- The process that connects Hermes to channels such as Telegram or Discord and routes messages.
- Session & memory
- A session holds conversation context, while memory keeps selected facts that should persist.
Chat with Hermes from Telegram, Discord, Slack, WhatsApp, Signal, SMS, Email, Home Assistant, Mattermost, Matrix, DingTalk, Yuanbao, Microsoft Teams, LINE, Raft, Webhooks, or any OpenAI-compatible frontend via the API server — architecture and setup overview
What does the source say, and in what order?
- 01Platform Comparison
Start here to understand the core idea or structure.
- 02Architecture
Read this after the foundation, then connect it to the previous step.
- 03Intentional Silence Tokens
Read this after the foundation, then connect it to the previous step.
- 04Quick Setup
Read this after the foundation, then connect it to the previous step.
- 05Gateway Commands
Read this after the foundation, then connect it to the previous step.
- 06Optional Linux event-loop watchdog
Read this after the foundation, then connect it to the previous step.
- 07Chat Commands (Inside Messaging)
Read this after the foundation, then connect it to the previous step.
- 08Session Management
Read this after the foundation, then connect it to the previous step.
- 09Session Persistence
Read this after the foundation, then connect it to the previous step.
- 10Finding Past Sessions (/sessions)
Finish here to verify the result and special cases.
Copy only after you understand the effect.
Each platform adapter receives messages, routes them through a per-chat session store, and dispatches them to the AIAgent for processing. The gateway also runs the cron scheduler, ticking every 60 seconds to execute any due jobs.
## Intentional Silence Tokens
For group chats, hooks, and automation flows, Hermes supports explicit silence tokens. If the agent's final response is exactly one supported token, the gateway suppresses outbound delivery and sends nothing to the chat.
Supported tokens:
- `[SILENT]`
- `SILENT`
- `NO_REPLY`
- `NO REPLY`
Whitespace and case are normalized, but the whFailed turns still surface as errors; Hermes does not hide failures just because the text resembles a silence token.
## Quick Setup
The easiest way to configure messaging platforms is the interactive wizard:This walks you through configuring each platform with arrow-key selection, shows which platforms are already configured, and offers to start/restart the gateway when done.
## Gateway CommandsRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.