Problem or Use Case

Route gateway/bot token specific Discord channels/threads directly into named Hermes profiles, while keeping the gateway owner profile isolated.
Related and complementary to: #18420

Proposed Solution

Shape:

gateway:
profile_routes:

name: Scribe Discord thread
platform: discord
chat_id: "1498997719094788097"
thread_id: "1498997719094788097"
profile: scribe
enabled: true

Behaviour:
Gateway profile still owns Discord auth/transport/reply delivery.
Matching route executes the target profile via subprocess isolation, e.g. hermes --profile scribe chat ..., not in-process profile mutation.
Target profile keeps its own config, model route, memory, sessions, skills, tools, and system prompt.
Route session continuity is persisted per route key.
/new or /reset inside the routed thread clears only that routed profile session.
Exact thread routes win over broader channel routes.

Why this matters: it gives teams “direct agent channels” — e.g. #scribe, #forge, #support-bot — without needing multiple Discord bots/tokens or unsafe runtime profile swapping. It also avoids the common footgun where a delegated/named agent is actually just the main profile pretending to be that agent.

Alternatives Considered

No response

Feature Type

New tool

Scope

Medium (few files, < 300 lines)

Contribution

• I'd like to implement this myself and submit a PR

Debug Report (optional)