Hermes QQ Bot Cannot Receive Group Messages Because the Group Event Is Not Handled (#63761)
Bug Tracker — July 13, 2026. A reported QQ Bot adapter event-name mismatch can leave group mentions unanswered while direct messages continue to work, creating a channel-specific availability gap that logs identify as an unhandled event.
Issue Summary
Issue #63761 reports that QQ group events arrive as GROUP_MESSAGE_CREATE, but the Hermes adapter handles only GROUP_AT_MESSAGE_CREATE. Logs show the received event as unhandled, so @ messages in groups receive no reply while DMs function. The issue describes a proposed one-line event-name correction, with linked PR #63765.
Observed Failure Path
| Step | Reported Behavior | User-Level Consequence |
|---|---|---|
| Group mention arrives | QQ emits GROUP_MESSAGE_CREATE. | Adapter must recognize the event before it can dispatch a response. |
| Adapter routing | Handler listens only for GROUP_AT_MESSAGE_CREATE. | Actual group event falls through as unhandled. |
| User interaction | @ message in a group receives no response. | Group channel appears unavailable despite working DMs. |
| Operations | Logs record the unexpected event name. | Root cause is observable, but only if event logs are reviewed. |
Operational Impact
Classification: P2. This page summarizes a publicly reported issue; scope and remediation status can change as the upstream project investigates and merges fixes. Teams should validate their own configuration and deployment before treating a workaround or update as complete.
Mitigation and Verification
- Test QQ DMs and group @ mentions separately after connector installation or upgrade; do not infer group readiness from a successful DM test.
- Alert on unhandled inbound event types and retain enough redacted event metadata to identify adapter coverage gaps.
- Track upstream issue #63761 and linked PR #63765, then retest the exact group-message flow after remediation.
- Use a channel acceptance checklist that covers permissions, event subscription names, and a real response round trip.
Source Evidence
Primary issue: NousResearch/hermes-agent issue #63761 (linked PR #63765)
For a managed-agent comparison, the relevant question is whether platform-policy failures and message-routing gaps fail clearly, preserve recoverability, and remain observable to operators—not only whether the happy path works.