website/docs/user-guide/messaging/yuanbao.md
Connect Hermes to Yuanbao, Tencent's enterprise messaging platform. The adapter uses a WebSocket gateway for real-time message delivery and supports both direct (C2C) and group conversations.
:::info Yuanbao is an enterprise messaging platform primarily used within Tencent and enterprise environments. It uses WebSocket for real-time communication, HMAC-based authentication, and supports rich media including images, files, and voice messages. :::
websockets and httpxaiofilesInstall the required dependencies:
pip install websockets httpx aiofiles
The easiest way to configure Yuanbao is through the interactive setup:
hermes gateway setup
Select Yuanbao when prompted. The wizard will:
:::tip The WebSocket URL and API Domain have sensible defaults built in. You only need to provide APP_ID and APP_SECRET to get started. :::
After initial setup, verify these variables in ~/.hermes/.env:
# Required
YUANBAO_APP_ID=your-app-id
YUANBAO_APP_SECRET=your-app-secret
YUANBAO_WS_URL=wss://api.yuanbao.example.com/ws
YUANBAO_API_DOMAIN=https://api.yuanbao.example.com
# Optional: bot account ID (normally obtained automatically from sign-token)
# YUANBAO_BOT_ID=your-bot-id
# Optional: internal routing environment (e.g. test/staging/production)
# YUANBAO_ROUTE_ENV=production
# Optional: home channel for cron/notifications (format: direct:<account> or group:<group_code>)
YUANBAO_HOME_CHANNEL=direct:bot_account_id
YUANBAO_HOME_CHANNEL_NAME="Bot Notifications"
# Optional: restrict access (legacy, see Access Control below for fine-grained policies)
YUANBAO_ALLOWED_USERS=user_account_1,user_account_2
hermes gateway
The adapter will connect to the Yuanbao WebSocket gateway, authenticate using HMAC signatures, and begin processing messages.
Yuanbao uses prefixed identifiers depending on conversation type:
| Chat Type | Format | Example |
|---|---|---|
| Direct message (C2C) | direct:<account> | direct:user123 |
| Group message | group:<group_code> | group:grp456 |
The Yuanbao adapter automatically handles media uploads via COS (Tencent Cloud Object Storage):
Media URLs are automatically validated and downloaded before upload to prevent SSRF attacks.
Use the /sethome command in any Yuanbao chat (DM or group) to designate it as the home channel. Scheduled tasks (cron jobs) deliver their results to this channel.
:::tip Auto-sethome If no home channel is configured, the first user to message the bot will be automatically set as the home channel owner. If the current home channel is a group chat, the first DM will upgrade it to a direct channel. :::
You can also set it manually in ~/.hermes/.env:
YUANBAO_HOME_CHANNEL=direct:user_account_id
# or for a group:
# YUANBAO_HOME_CHANNEL=group:group_code
YUANBAO_HOME_CHANNEL_NAME="My Bot Updates"
/sethomeCreate a cron job:
/cron "0 9 * * *" Check server status
The scheduled output will be delivered to your Yuanbao home channel every day at 9 AM.
Send any message to the bot in Yuanbao:
hello
The bot responds in the same conversation thread.
All standard Hermes commands work on Yuanbao:
| Command | Description |
|---|---|
/new | Start a fresh conversation |
/model [provider:model] | Show or change the model |
/sethome | Set this chat as the home channel |
/status | Show session info |
/help | Show available commands |
To send a file to the bot, simply attach it directly in the Yuanbao chat. The bot will automatically download and process the file attachment.
You can also include a message with the attachment:
Please analyze this document
When you ask the bot to create or export a file, it sends the file directly to your Yuanbao chat.
Cause: Authentication failed during WebSocket handshake.
Fix:
tail -f ~/.hermes/logs/gateway.logCause: WebSocket URL is unreachable or incorrect.
Fix:
wss://)curl -I https://[YUANBAO_API_DOMAIN]Cause: COS credentials are invalid or media server is unreachable.
Fix:
Cause: Home channel ID format is incorrect or cron job hasn't triggered.
Fix:
/sethome command to auto-detect correct format/statusCause: WebSocket connection is unstable or network is unreliable.
Fix:
HERMES_LOG_LEVEL=debugYuanbao supports fine-grained access control for both DM and group conversations:
# DM policy: open (default) | allowlist | disabled
YUANBAO_DM_POLICY=open
# Comma-separated user IDs allowed to DM the bot (only used when DM_POLICY=allowlist)
YUANBAO_DM_ALLOW_FROM=user_id_1,user_id_2
# Group policy: open (default) | allowlist | disabled
YUANBAO_GROUP_POLICY=open
# Comma-separated group codes allowed (only used when GROUP_POLICY=allowlist)
YUANBAO_GROUP_ALLOW_FROM=group_code_1,group_code_2
These can also be set in config.yaml:
platforms:
yuanbao:
extra:
dm_policy: allowlist
dm_allow_from: "user1,user2"
group_policy: open
group_allow_from: ""
Yuanbao has a maximum message size. Hermes automatically chunks large responses with Markdown-aware splitting (respects code fences, tables, and paragraph boundaries).
The following connection parameters are built into the adapter with sensible defaults:
| Parameter | Default Value | Description |
|---|---|---|
| WebSocket connect timeout | 15 seconds | Time to wait for WS handshake |
| Heartbeat interval | 30 seconds | Ping frequency to keep connection alive |
| Max reconnect attempts | 100 | Maximum number of reconnection tries |
| Reconnect backoff | 1s → 60s (exponential) | Wait time between reconnect attempts |
| Reply heartbeat interval | 2 seconds | RUNNING status send frequency |
| Send timeout | 30 seconds | Timeout for outbound WS messages |
:::note These values are currently not configurable via environment variables. They are optimized for typical Yuanbao deployments. :::
Enable debug logging to troubleshoot connection issues:
HERMES_LOG_LEVEL=debug hermes gateway
Schedule tasks that run on Yuanbao:
/cron "0 */4 * * *" Report system health
Results are delivered to your home channel.
Run long operations without blocking the conversation:
/background Analyze all files in the archive
Send a message from CLI to Yuanbao:
hermes chat -q "Send 'Hello from CLI' to yuanbao:group:group_code"