Running Many Gateways at Once
Running Many Gateways at Once
Start with meaning, then move to detail.
This lesson explains Running Many Gateways at Once as part of operating Hermes with explicit security boundaries. 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 When to use this, Quick start, Alternative: one gateway for all profiles (multiplexing), then verify failure modes and version compatibility.
You only need to know which files and accounts the agent may access.
A clear outcome before you read.
- Understand Running Many Gateways at Once 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.
What does the source say, and in what order?
- 01When to use this
Start here to understand the core idea or structure.
- 02Quick start
Read this after the foundation, then connect it to the previous step.
- 03Alternative: one gateway for all profiles (multiplexing)
Read this after the foundation, then connect it to the previous step.
- 04When to prefer multiplexing
Read this after the foundation, then connect it to the previous step.
- 05How to opt in
Read this after the foundation, then connect it to the previous step.
- 06What changes when multiplexing is on
Read this after the foundation, then connect it to the previous step.
- 071. Secondary profiles must not start their own gateway
Read this after the foundation, then connect it to the previous step.
- 082. HTTP-inbound platforms are reached via a /p/<profile>/ URL prefix
Read this after the foundation, then connect it to the previous step.
- 093. Per-credential platforms still need their own token per profile
Read this after the foundation, then connect it to the previous step.
- 104. Session keys are namespaced by profile
Finish here to verify the result and special cases.
Copy only after you understand the effect.
# Create profiles (once)
hermes profile create coder
hermes profile create personal-bot
hermes profile create research
# Configure each
coder setup
personal-bot setup
research setup
# Install each gateway as a managed service
coder gateway install
personal-bot gateway install
research gateway install
# Start them all
coder gateway start
personal-bot gateway start
research gateway starthermes config set gateway.multiplex_profiles true
hermes gateway restartgateway:
multiplex_profiles: trueRead 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.