Files
agent-estate-wiki/runbooks/multiplexer-setup.md
T
Hermes 341dda95dd stocktake 2026-11-11: 36 stale pages re-verified (0 stale); fallback chain rewritten 4/6 slots; CT333 'clawtest' naming claim corrected; nous 404 credits signature replaces refresh-token 401; estate shrank (VM 310 + CT601 gone)
- freshness: 36 stale / 93 fresh / 3 no-date -> 0 stale / 129 fresh / 3 no-date of 132 (same-day report regenerated after the corrections, per pattern 13)
- skills: 299 skills / 67 categories (count unchanged; generator arithmetic re-verified by hand against the live tree: 300 SKILL.md files - 1 nested duplicate = 299)
- runbooks/test-openrouter: live fallback chain rewritten (primary back to smart-route/custom:omni-101; mimo-v2.5, stepfun, qwen3.5/ollama-cloud out; guacano + kilo-reflection-beam-free in); ollama.com dropped from the URL test list; guacano/litellm noted as internal + key-gated
- comparisons/hermes-vs-nanobot: the 2026-10-20 'CT333 is zeroclaw in Proxmox naming' claim was itself wrong - pct list and hostname both return clawtest
- incidents/2026-10-22-nous: refresh-token failure gone from logs; new signature 404 insufficient_credits_for_paid_model from auxiliary.pulse_memory (ninth slot, back on nous, paid model) - open item revised
- incidents/2026-08-29-gmail: email crons now ok but root cause unfixed 74 days (himalaya message read still in fetch_newsletters.py; goimapnotify back up PID 441; monitor still paused)
- 30 further pages re-verified live and de-flagged with dated probe notes (ct207 ingress, CT205 guanaco v0.8.15, CT270 nextcloud 33.0.2.2, headless stack, hermes-ui both hosts, systemd units + cgroup limits, terminal/tool_search/mnemosyne/custom_providers config blocks, ops profile still deleted, hosts/pve guest lists)
- log.md addendum + index.md date bump; no page deleted, no secrets written
2026-11-11 03:52:48 +08:00

123 lines
4.4 KiB
Markdown

---
title: Multiplexer Setup (Multi-Profile Gateway)
type: runbook
status: active
created: 2026-07-28
updated: 2026-11-11
verified_on: 2026-11-11
confidence: high
tags: [hermes, multiplexer, telegram, profiles, gateway]
---
# Multiplexer Setup
## What It Is
One gateway process serving multiple Hermes profiles through a single Telegram bot. Messages are routed to the correct profile by `profile_routes` (chat_id → profile).
## Architecture
```
Telegram Bot (single token)
│
▼
Default Gateway (multiplex_profiles: true)
│
├── profile_routes: chat_id → profile
│
├── default profile (Rhino chat: -1004321904721)
└── ops profile (Tusk ops: -1003914987043, -1003932503629)
```
## Key Config Locations
### Default profile: `~/.hermes/config.yaml`
```yaml
gateway:
multiplex_profiles: true
profile_routes:
- name: ops-group
platform: telegram
chat_id: '-1003914987043'
profile: ops
- name: ops-group-2
platform: telegram
chat_id: '-1003932503629'
profile: ops
telegram:
allowed_chats: '-1004321904721,-1003914987043,-1003932503629'
group_allowed_chats: '-1004321904721,-1003914987043,-1003932503629'
```
### Ops profile: `~/.hermes/profiles/ops/config.yaml`
```yaml
telegram:
allowed_chats:
- '-1003914987043'
- '-1003932503629'
group_allowed_chats:
- '-1003914987043'
- '-1003932503629'
platforms:
telegram:
enabled: false # ← DISABLED — multiplexer handles this
```
## ⚠ The `ops` profile was DELETED on 2026-10-11 (verified 2026-10-20)
`/home/hermes/.hermes/profiles/` now contains **only** `.deleted/ops` (an 8-byte marker file whose
entire content is the word `deleted`, dated 2026-10-11). **`~/.hermes/profiles/ops/` no longer
exists** — there is no `config.yaml`, no `SOUL.md`, no profile directory.
**But the default profile still routes to it.** `~/.hermes/config.yaml` still carries both
`profile_routes` entries (`ops-group` → `-1003914987043`, `ops-group-2` → `-1003932503629`,
both `profile: ops`), and `multiplex_profiles: true` is still set. The ops SOUL (Tusk, the African
elephant) and its `allowed_chats` list are gone with the directory.
**Consequence:** messages arriving in the two ops chats have a route pointing at a profile that no
longer exists. Treat the "Ops profile" blocks below as **historical** — the second profile's
config can no longer be read at `~/.hermes/profiles/ops/config.yaml` because that path is gone.
**Two things need a decision (not actioned here):**
1. Should `profile_routes` be removed, or should the `ops` profile be recreated?
2. Is the `multiplex_profiles: true` + two-route configuration still needed at all?
Until that is settled, treat the ops chat IDs as **possibly unroutable** and verify the gateway
actually resolves them before relying on this runbook.
> **Re-probed 2026-11-11 — the situation is unchanged and the two open decisions are still open.**
> /home/hermes/.hermes/profiles/` contains **only** `.deleted/ops` (8-byte marker reading
> `deleted`, dated 2026-10-11); `~/.hermes/profiles/ops/` still does not exist. The default
> profile's config **still** carries `multiplex_profiles: true` and both `profile_routes` entries
> (`ops-group` → `-1003914987043`, `ops-group-2` → `-1003932503629`, both `profile: ops`), and
> `telegram.allowed_chats` / `group_allowed_chats` still list all three chat IDs. So the two ops
> chats still route to a profile that no longer exists — **31 days unresolved**.
## The Silent-Drop Pitfall
The `allowed_chats` gate runs on the **default profile's adapter** BEFORE `profile_routes` stamps `source.profile`. If a chat is only authorized in the secondary profile's config but not the default's, messages from that chat are silently dropped.
**Moral:** When adding a new chat for a secondary profile, add it to BOTH profiles' `allowed_chats`.
## Adding a New Group
1. Add the chat_id to the default profile's `profile_routes`
2. Add the chat_id to the ops profile's `allowed_chats` and `group_allowed_chats`
3. **Add the chat_id to the default profile's `allowed_chats` and `group_allowed_chats`** (comma-separated list)
4. Restart the gateway: `systemctl --user restart hermes-gateway`
## Restarting
From an SSH shell (outside the agent process):
```bash
systemctl --user restart hermes-gateway
```
## Related
- [[hermes-agent]]
- [[messaging-integrations]]