The core of Hermes Agent is to create applications on q.qq.com first, and then distribute QQ_APP_ID and QQ_CLIENT_SECRET to the gateway. The official documentation also reminds that many permissions and allowlists here in QQ use OpenID, not the QQ number or nickname you usually see.
How to match
- First, build an application on the QQ Bot development platform and get the App ID and Secret.
- Confirm that the required intents are already open, such as C2C, group messages, and Guild messages.
- Write
QQ_APP_ID,QQ_CLIENT_SECRETin.env. - Refill
QQBOT_HOME_CHANNELwhen cron or proactive notification is required. - DM and group chat permissions are allocated separately, so don't confuse global opening and group openness into one thing.
This integration is valuable if you are working on a Chinese team scenario, but only if you first understand OpenID, sandbox routing, and permission models.
In a word: The biggest pitfall of QQ Bot is not that it can't be connected, but that it treats QQ numbers, nicknames, and OpenID as the same thing.
Official open source address: https://github.com/NousResearch/hermes-agent; Official document entry: https://hermes-agent.nousresearch.com/.
