@deepseek-ai/dsh-qqbot

QQ 官方机器人桥接：通过 WebSocket 网关接入 QQ，把一个会话选为「QQ 大脑」——群聊 @消息和私聊消息作为普通用户消息进入该会话，回复发回 QQ。

This is an out-of-tree plugin: it does not live in the harness source tree and resolves from the active profile's node_modules.

Installation

Build it, then install it into the profile you run:

pnpm install
pnpm run build
cd "$env:DSH_HOME/profiles/"     # e.g. web
pnpm add E:/Project/dsh-qqbot

Then mount it in $DSH_HOME/cordis.patch.yml (applies to every profile) or the profile's own cordis.patch.yml:

- insert:
    - id: qqbot
      name: '@deepseek-ai/dsh-qqbot'
      config:
        appId: '1904004435'
        appSecret: ''

The peer dependencies (@deepseek-ai/cordis, the @deepseek-ai/dsh-* Service Definitions) are resolved through the profile's own node_modules and the harness-maintained $DSH_HOME/profiles/node_modules fallback, so they are not re-installed here.

Configuration

The plugin is a function plugin (name: 'qqbot', inject: ['agents', 'commands']). Mount it in a Cordis composition with the robot identity; a session opts in at runtime with /qqbot on.

Field	Env fallback	Required	Meaning
appId	QQBOT_APP_ID	yes	Robot application id from the QQ open platform.
appSecret	QQBOT_APP_SECRET	yes	Robot application secret; never logged or put in a prompt.
sandbox	—	no	Route token, gateway, and sends through the sandbox host. Default false.

Missing credentials fail at load. Credentials resolve from config first, then from the two environment variables, so a deployment can keep the secret out of cordis.yml.

Behavior

• /qqbot on binds the dispatching agent — its session history and cwd are reused unchanged — registers the channel prompt on that agent's scope, and connects the gateway. disconnects and drops the binding; disposing the bound session also drops it. Nothing connects until a session opts in.