hermes - 💡(How to fix) Fix [Feature]: Support multiple QQ Bot instances in a single Hermes daemon [1 participants]

Problem or Use Case

I want to connect two different QQ Bot accounts (different App ID / App Secret) to the same Hermes instance, so I can have two independent sessions running in parallel — e.g., one bot for long-running tasks and another for interactive conversation.

Currently, the QQ Bot adapter only supports a single instance because:

• Environment variables are singular (QQ_APP_ID, QQ_CLIENT_SECRET) — no way to configure a second bot
• platforms.qq in config.yaml is a single config block, not an array

This is a general limitation that likely applies to other messaging platform adapters as well (Telegram, Discord, etc.).

Proposed Solution

Support multiple named instances per platform in config.yaml:

platforms:
  qq:
    instances:
      - name: "bot-primary"
        app_id: "APP_ID_1"
        client_secret: "SECRET_1"
        home_channel: "OPENID_1"
      - name: "bot-secondary"
        app_id: "APP_ID_2"
        client_secret: "SECRET_2"
        home_channel: "OPENID_2"

Each instance would:

• Maintain its own WebSocket gateway connection
• Have its own independent sessions and home channel
• Be addressable by name for send_message targeting

Environment variables could follow a naming convention like QQ_APP_ID_1 / QQ_APP_ID_2, or QQ_APP_ID_PRIMARY.

Alternatives Considered

1. Running two separate Hermes instances (different HERMES_HOME) — works but is operationally expensive: duplicate config, separate processes, no shared memory, double maintenance overhead.
2. Single bot with session isolation — already works per-channel, but does not solve the parallel-interaction use case (user sees one bot window, not two).

Feature Type

Gateway / messaging improvement

Scope

Large (new module or significant refactor)

Contribution

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