dsh-qqbot
在终端中运行以下命令:
dsh plugin install cafeawa/dsh-qqbot
将以下提示词粘贴到 DeepSeek Harness 对话框中:
在已可用的 DeepSeek Harness 环境中执行 dsh plugin install cafeawa/dsh-qqbot 即可安装,插件源码地址为 https://github.com/cafeawa/dsh-qqbot,安装后在 profile 的 cordis.patch.yml 中填入 QQ Bot 凭据即可启动。
插件介绍
No matter how capable a DeepSeek Harness agent is, the friction of reaching for a terminal or WebUI before every interaction adds up. dsh-qqbot removes that step by turning QQ into a first-class frontend for your dsh agent: send a message in a private or group chat from your phone, and the agent handles tool execution, model switching, and session management in the background, then streams the reply back through QQ.
Beyond chat, the plugin addresses the details that matter in daily use. Group chats support @bot triggering, quoted-message context, and file-attachment downloads; private chats deliver streaming replies with Markdown chunking. Sessions are isolated per peer, reclaimed after idle timeouts, and restored across restarts. Model routing is flexible—set a per-peer preference, configure via settings.yaml, or fall back to the host default. Built-in commands such as /bot-model, /bot-reset, /bot-status, and /goal cover the most common operations. The approval bridge keeps workflows tight: when the agent needs confirmation, a button or text prompt appears in QQ while the WebUI shows it in sync, so you never have to hop between surfaces. Long-running goal tasks send a completion notification when they finish.
If you live in QQ, want to invoke your dsh agent from a phone or tablet, or prefer handling approvals inside an IM chat rather than a terminal, dsh-qqbot is ready to go out of the box. It is written from scratch with no reliance on Tencent-internal code; the underlying protocol uses the MIT-licensed @tencent-connect/qqbot-nodejs, making it compliant, self-hostable, and easy to audit.
使用场景
- 在手机上通过 QQ 私聊随时随地调用 dsh agent 执行工具和切换模型
- 在群聊中 @bot 发起对话,通过 QQ 按钮完成审批,无需切回终端
- 为不同群和好友配置独立会话与模型偏好,长任务完成后收到通知
适合人员
- 日常使用 QQ、希望手机上手操作 dsh agent 的用户
- 以 QQ 群聊为主要协作场景、需要在 IM 内完成审批的团队
- 偏好自托管、MIT 许可、无闭源依赖的 QQ Bot 集成方案的开发者