​

QQ Bot

​

At A Glance

​

Minimal Config

[qqbot]
enabled = true
app_id_env = "QQBOT_APP_ID"
client_secret_env = "QQBOT_CLIENT_SECRET"
allowed_peer_ids = ["openid_alice"]

​

Smoke Test

loong channels send qqbot --target "c2c:openid_alice" --text "hello from loong"
loong channels serve qqbot

• QQ Bot [qqbot] appears in the gateway-supervised runtime set
• channels serve qqbot starts a native Loong-owned runtime instead of a managed plugin selection flow
• doctor keeps direct send / serve readiness checks visible and actionable

​

Current Command Surface

​

Required Fields For Send

​

Required Fields For Serve

​

Stable Target Templates

​

Account Scope Note

​

Runtime Notes

• QQ Bot no longer depends on managed bridge discovery for its main shipped runtime path.
• The native runtime uses the configured QQ gateway credentials directly.

​

Gateway And Ownership

​

Operator Notes

• Keep allowed_peer_ids explicit and narrow.
• Loong validates allowed_peer_ids locally before forwarding a QQ send, so a mistyped openid is rejected before it reaches the upstream gateway.
• channels serve qqbot owns the runtime loop directly; failures belong to the native runtime path instead of an external managed-plugin selection layer.
• Treat QQ Bot as a multi-account surface from the start if you expect separate direct, group, or guild identities.

​

Related Docs

• Continue to Weixin for the WeChat bridge-first lane.
• Continue to OneBot when the upstream bridge already speaks OneBot v11.
• Continue to Gateway And Supervision when QQ Bot should join a longer-lived supervised runtime.
• Continue to Channel Setup for the shared public setup contract.