hermes - 💡(How to fix) Fix feat(telegram): channel_profiles — route Telegram chats to Hermes profiles in one gateway

Summary

Allow a single Telegram bot (one gateway process) to route messages from different chats/groups/DMs to different Hermes profiles via a simple channel_profiles config map.

Motivation

Right now, one gateway = one profile. To have different agent personalities per chat, you must run separate gateway processes with separate bot tokens (Pattern B in the multi-profile docs). This works but wastes RAM (~200MB per extra gateway) and requires managing multiple @BotFather tokens.

The backend is now ready: PRs #39921 + #39993 made the gateway WebSocket protocol profile-aware — session.create, session.resume, and prompt.submit all accept a profile parameter. One dashboard process can run agent turns as ANY profile on the host, loading that profile's config, SOUL.md, skills, model, and state.db.

What's missing: the Telegram adapter layer that reads a route config and passes profile to the session calls.

Proposed config

telegram:
  channel_profiles:
    "-1001234567890": "crypto"       # group → crypto profile
    "-1009876543210": "coder"         # group → coder profile
    "56005800": "default"             # DM → default (optional)

When a message arrives from a chat listed in channel_profiles, the gateway:

1. Resolves profile = channel_profiles[chat_id] (falls back to gateway's launch profile)
2. Passes profile to session.create / session.resume / prompt.submit
3. The existing profile-aware backend handles the rest — loads correct HERMES_HOME, config, SOUL, state.db

Scope

Why now

The blocking prerequisite (gateway profile-aware protocol) landed in main this week (#39921 Jun 5, #39993 Jun 5). Before these PRs, the gateway was hard-bound to one HERMES_HOME and could not run turns under different profiles. That architectural barrier is gone.

Related

• #29535 — profile_routes (broader, platform-agnostic version of this)
• #24913 — /profile <name> slash command
• #10143 — Topic-to-Profile routing
• #39921 — Gateway: profile-aware session.resume + prompt.submit
• #39993 — Gateway: profile-aware session.create