dsh-qq-bridge

Connect DeepSeek Harness (DSH) to a QQ bot through the OneBot 11 HTTP API (NapCat / Lagrange / go-cqhttp compatible).

It ships three host tools:

Tool	Access	What it does
qq_group_list	read	List QQ groups the bot has joined.
qq_recent_messages	read	Read the latest messages of one group as sender: text lines.
qq_send_message	write, off by default	Send a plain-text message to a group.

Requirements

• A running OneBot 11 implementation with the HTTP API enabled, reachable from the machine that runs DSH.
• Node.js 20+ (DSH already ships one).

Install

dsh plugin add dsh-qq-bridge

or install the package directory through the DSH plugin manager.

Configure

Plugin settings:

Key	Default	Meaning
endpoint	http://127.0.0.1:6199	OneBot HTTP API base URL.
accessToken	empty	Sent as Authorization: Bearer <token> when set.
allowSend	false	Must be turned on before qq_send_message will post anything.
timeoutMs	10000	Per-request timeout.

Example: NapCat with HTTP server on 127.0.0.1:6199 and a token secret:

{ "endpoint": "http://127.0.0.1:6199", "accessToken": "secret", "allowSend": true }

Notes

• The group id and message text are sent to your OneBot endpoint only; no other network calls are made.
• qq_send_message is disabled by default so the model cannot post to QQ without an explicit opt-in.
• The plugin never stores tokens itself; configuration lives in the DSH profile.

NapCat / OneBot 11 setup

1. In NapCat's WebUI open 网络配置 → HTTP 服务器, add one with a port and a token, then restart the container so the adapter starts.

2. Make sure the port is reachable from the machine running DSH (publish the container port, proxy it behind nginx, or forward it over SSH).

3. In the DSH plugin settings set:

   • endpoint: the OneBot 11 HTTP base URL, e.g. http://127.0.0.1:3010
   • accessToken: the token from step 1
   • allowSend: keep off until you want the model to post messages

NapCat calls the HTTP adapter for both reads and writes; with allowSend off the plugin only exposes read tools that actually send.