Gateway Internals
Gateway Internals
Start with meaning, then move to detail.
This lesson explains Gateway Internals 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 Key Files, Architecture Overview, Message Flow, then verify failure modes and version compatibility.
Know Python, Git, and basic project structure before changing code.
A clear outcome before you read.
- Understand Gateway Internals 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.
How the messaging gateway boots, authorizes users, routes sessions, and delivers messages
What does the source say, and in what order?
- 01Key Files
Start here to understand the core idea or structure.
- 02Architecture Overview
Read this after the foundation, then connect it to the previous step.
- 03Message Flow
Read this after the foundation, then connect it to the previous step.
- 04Session Key Format
Read this after the foundation, then connect it to the previous step.
- 05Two-Level Message Guard
Read this after the foundation, then connect it to the previous step.
- 06Authorization
Read this after the foundation, then connect it to the previous step.
- 07DM Pairing Flow
Read this after the foundation, then connect it to the previous step.
- 08Slash Command Dispatch
Read this after the foundation, then connect it to the previous step.
- 09Running-Agent Guard
Read this after the foundation, then connect it to the previous step.
- 10Config Sources
Finish here to verify the result and special cases.
Copy only after you understand the effect.
┌─────────────────────────────────────────────────┐
│ GatewayRunner │
│ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ Telegram │ │ Discord │ │ Slack │ │
│ │ Adapter │ │ Adapter │ │ Adapter │ │
│ └────┬─────┘ └────┬─────┘ └────┬─────┘ │
│ │ │ │ │
│ └─────────────┼─────────────┘ │
│ ▼ │
│ _handle_message() │
│ │ agent:main:{platform}:{chat_type}:{chat_id}Admin: /pair
Gateway: "Pairing code: ABC123. Share with the user."
New user: ABC123
Gateway: "Paired! You're now authorized."Read 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.