Preface

DSH developers sometimes need to deploy Agents within QQ: to follow up in private chats or trigger tasks in group chats. If you only wish to connect messages without introducing personal QQ reverse engineering protocols, hooks, injection, or simulated logins, dsh-qqbot-bridge is introduced below.

What is This

dsh-qqbot-bridge is a DSH plugin based on the Tencent official QQ bot open platform that safely integrates QQ private chats or group chats into DeepSeek Harness (DSH).

  • Maintainer: dsh-qqbot-bridge contributors
  • Current Version: 0.1.0
  • License: MIT
  • Ownership clues in the materials are inconsistent; this article does not assert final ownership based on them.

Sending a message to the bot is equivalent to sending a message to a standalone DSH Agent session.

Core Capabilities

  • Uses only the Tencent QQ bot open platform and official Tencent SDKs; does not use personal QQ reverse engineering protocols, hooks, injection, or simulated logins.
  • Supports official Tencent QR code binding on first startup; automatically saves AppID, Secret, and the OpenID of the scanned user.
  • Private chats are whitelisted by default; group chats are disabled by default. The whitelist does not degrade to open access.
  • QQ messages directly drive DSH Agents, supporting streaming replies, automatic retry on send failure, session persistence, and model switching.
  • Supports handling one-time DSH permission requests within QQ: /approve CODE or /deny CODE.
  • AppSecret, OpenID, and API Key are stored only locally in $DSH_HOME/.env, not entering project configuration or logs.
  • Built-in privacy scan, unit tests, packaging checks, and GitHub Actions CI.

Installation and Enabling

Plugin Commands

The following are verified npm post-install commands.

dsh plugin --profile qqbot add dsh-qqbot-bridge
dsh --profile qqbot

Starting from Source

The following startup commands come from verified examples; the repository path is inconsistent in materials, please verify the actual repository before use.

Windows

git clone https://github.com/JHf0912/dsh-qqbot-bridge.git
cd dsh-qqbot-bridge
powershell -ExecutionPolicy Bypass -File .\scripts\dev-start.ps1

Linux/macOS

git clone https://github.com/JHf0912/dsh-qqbot-bridge.git
cd dsh-qqbot-bridge
chmod +x scripts/dev-start.sh
./scripts/dev-start.sh

Common parameters for the startup script:

  • --profile name
  • --skip-install
  • --build-only
  • --setup-only

Setting Required API Key

DEEPSEEK_API_KEY must be set; otherwise, the bot cannot generate any replies.

It is recommended to write the key into the local DSH environment file:

# Windows default location: C:\Users\<Your User>\.dsh\.env
# macOS/Linux default location: ~/.dsh/.env
DEEPSEEK_API_KEY="Your API Key"

On Windows, you can also append it to the default location:

$key = Read-Host -Prompt "Paste your DeepSeek API Key"
Add-Content "$env:USERPROFILE\.dsh\.env" "DEEPSEEK_API_KEY=`"$key`""

First Scan and Whitelist

On the first startup, use the Tencent official QR code binding. After successful binding, the plugin will save the AppID, Secret, and the OpenID of the scanned user.

Note: The QQBOT_C2C_ALLOW whitelist written on the first scan is not injected into the current process. After the first scan, you need to stop and run it again; only then will QQ messages be accepted according to the whitelist policy.

Approvals within QQ

When DSH triggers a one-time permission request, you can handle the verification code within QQ. Examples are as follows:

/approve A1B2C3
/deny A1B2C3

Approval boundaries are as follows:

  • Only the task initiator themselves can process it.
  • Verification codes are one-time use.
  • Default 120-second timeout auto-reject.

Privacy and Runtime Notes

  • The plugin runs with the current dsh process permissions; you should check the source code and license before installation.
  • Requires Node.js >= 22.
  • Windows dev-start.ps1 does not include a node existence check.
  • The current version is 0.1.0; the project is still in its early stages. It is recommended to use a dedicated test bot, a dedicated working directory, and a private chat whitelist first.
  • DEEPSEEK_API_KEY must be set.
  • Sensitive configurations should be saved in $DSH_HOME/.env; do not commit or paste them into Issues, PRs, screenshots, or logs.
  • Follow Tencent QQ open platform rules, bot operation guidelines, and local laws and regulations before use.
  • The project cannot guarantee that the account will definitely not be restricted, nor does it provide implementations to bypass risk control or protocol restrictions.

Conclusion

The value of dsh-qqbot-bridge lies in: connecting QQ and DSH using Tencent’s official bot capabilities, and handling access control, key storage, and one-time approvals on the plugin side.

The community directory is an independent site and has no official affiliation with DeepSeek / High-Flyer; verified materials do not provide a directory page URL.

The GitHub path is inconsistent in materials; please manually verify before use:

  • https://github.com/wang-22-code/dsh-qqbot-bridge
  • https://github.com/JHf0912/dsh-qqbot-bridge