From e90869e887c09ed3c1193ac0911fcf454c7bbfad Mon Sep 17 00:00:00 2001 From: William Chen <57119977+OCWC22@users.noreply.github.com> Date: Tue, 12 May 2026 15:21:26 -0700 Subject: [PATCH] Document Telegram multi-profile gateway commands --- website/docs/user-guide/messaging/telegram.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/website/docs/user-guide/messaging/telegram.md b/website/docs/user-guide/messaging/telegram.md index 57ecc50d40f..b68a8f82bd3 100644 --- a/website/docs/user-guide/messaging/telegram.md +++ b/website/docs/user-guide/messaging/telegram.md @@ -328,6 +328,22 @@ With this setup, a group message like `@research_bot @ops_bot summarize this` is Set `exclusive_bot_mentions: false` only for legacy groups where explicit mentions should not override reply and wake-word triggers. +To operate several profiles, run the gateway command once per profile. For example: + +```bash +# default profile +hermes gateway start +hermes gateway status +hermes gateway stop + +# named profiles +hermes -p research gateway start +hermes -p research gateway status +hermes -p research gateway stop +``` + +For a small fixed fleet, use a shell loop or script that calls `hermes gateway ` for the default profile and `hermes -p gateway ` for each named profile. This is more reliable than assuming a single process-level command controls every named profile on every service manager. + ### Troubleshooting: works in DMs but not groups If the bot responds in a private chat but stays silent in a group, check these