Lesson 578 of 2116
Gateway Sessions Across Discord, Slack, and CLI
Design session keys so one agent can talk through many surfaces without mixing users or channels.
Lesson map
What this lesson covers
Learning path
The main moves in order
- 1What the local Hermes build teaches
- 2gateway
- 3session key
- 4adapter
Concept cluster
Terms to connect while reading
Section 1
What the local Hermes build teaches
This build lab focuses on the session model that lets messaging gateways feel continuous without leaking context. The goal is not to copy a private machine setup. The goal is to learn the architecture pattern well enough to build a small, classroom-safe version.
Every incoming message should be normalized into a session source: platform, workspace, channel, thread, user, and persona.
Compare the options
| Hermes pattern | Student build | Risk to handle |
|---|---|---|
| Name the boundary | a session-key design for CLI, Discord, Slack, and a classroom web chat | using only a username as identity and accidentally merging two different people, classes, or channels |
| Keep the interface small | Start with one happy path and one failure path | Avoid a demo that only works when everything is perfect |
| Make the system observable | Log decisions, status, and errors in plain language | Do not log private data or secrets |
Build the small version
- 1Draw or write a session-key design for CLI, Discord, Slack, and a classroom web chat.
- 2Mark which parts are user-facing, which parts are internal, and which parts require approval.
- 3Choose one low-risk workflow and implement only that workflow first.
- 4Add one failure case before adding a second feature.
- 5Write a short operator note: what the agent may do, what it must ask about, and what it must never do.
A classroom-safe skeleton inspired by the local Hermes architecture scan.
session_key = join(
platform, # cli, discord, slack, web
workspace_id, # server, team, class, or local profile
channel_id,
thread_id,
user_id,
persona_id
)Key terms in this lesson
The big idea: session key is not decoration. It is part of the product architecture students need before an agent becomes safe enough to use with real people.
End-of-lesson quiz
Check what stuck
15 questions · Score saves to your progress.
Tutor
Curious about “Gateway Sessions Across Discord, Slack, and CLI”?
Ask anything about this lesson. I’ll answer using just what you’re reading — short, friendly, grounded.
Progress saved locally in this browser. Sign in to sync across devices.
Related lessons
Keep going
Creators · 24 min
Add a Messaging Platform Adapter
Turn the Hermes platform-adapter checklist into a student build plan for adding a new chat surface.
Creators · 19 min
Delivery Routing for Cron and Agent Outputs
Create a delivery router so agent outputs land in the right channel, format, and approval state.
Creators · 50 min
Evaluating Agent Performance: SWE-bench, WebArena, GAIA
Numbers on leaderboards are seductive and often wrong. Learn the big benchmarks, their leaderboard positions, their recently-exposed cheats, and how to run your own evals.