hermes - 💡(How to fix) Fix QQBot: send_message always fails with 'no access_token in response' despite gateway WebSocket being connected [1 pull requests]

Bug Description

When using send_message tool to send a message via QQBot, it always returns:

QQBot: no access_token in response

This happens even though the gateway WebSocket connection to QQ Bot is successfully established and receiving messages (the gateway log shows Ready, session_id=... and inbound C2C messages arrive fine).

Root Cause Analysis

The send_message tool appears to use a separate code path from the gateway's WebSocket connection. Instead of sending through the established WebSocket, it tries to call the QQ Bot REST API directly and needs a fresh access_token.

The gateway's qqbot adapter already has a valid access_token in memory (refreshed at startup), but send_message cannot access this in-memory token. When it tries to get its own token using the app_id/client_secret, it fails with "no access_token in response".

Log Evidence

Gateway log shows WebSocket OK:

[QQBot:1903879172] Ready, session_id=cf797649-b571-4e0e-8cf9-dac2849a9768

But send_message immediately returns:

QQBot: no access_token in response

Environment

• Hermes Agent v0.12.0 (2026.4.30)
• Platform: QQBot (single platform)
• Config: qqbot enabled with app_id + client_secret in .env

Possible Solutions

1. Route send_message through the gateway's existing WebSocket instead of REST API
2. Share the in-memory access_token between the gateway adapter and the send_message tool
3. Fix the token refresh logic in the standalone code path

Related

#21026 - Gateway multi-platform single asyncio event loop architecture issue