@tencent-connect/dsh-qqbot

Q: Does it collide with @xmanrui/dsh-im?

@tencent-connect/dsh-qqbot is the one to keep here: It peers dsh-user-approval and @deepseek-ai/dsh-session, so approvals round-trip through the session that will run the tool.

Q: What happens when dsh upgrades?

Nothing declares a version window for @tencent-connect/dsh-qqbot: dsh --version tells you what you are running, and no check will tell you whether @tencent-connect/dsh-qqbot matches it.

Chat with DSH inside QQ private and group chats.

Version 0.5.5 of @tencent-connect/dsh-qqbot, last published 2026-10-30; the install command and the range come from its own manifest.

Install

dsh plugin add @tencent-connect/dsh-qqbot writes one dependency line into the profile manifest; pnpm then unpacks it under $DSH_HOME/profiles/<name>/node_modules.

dsh plugin --profile web add @tencent-connect/dsh-qqbot

Compatibility

@tencent-connect/dsh-qqbot ships no engines.dsh entry, so nothing checks it against your CLI version at boot. Read the npm page before installing.

If two plugins fight

Peers @deepseek-ai/dsh-agent, @deepseek-ai/dsh-llm, @deepseek-ai/dsh-session and @deepseek-ai/dsh-user-approval: it drives real agents and asks for approval in QQ. With @xmanrui/dsh-im installed, QQ messages arrive twice through two different bridges.

Who made it

Author: tencent-connect. Repository: https://github.com/tencent-connect/dsh-qqbot. Package page: https://www.npmjs.com/package/@tencent-connect/dsh-qqbot.

After install

It declares @deepseek-ai/cordis as a peer and renders a remote entry point in the profile a client connects to; after dsh plugin add @tencent-connect/dsh-qqbot, dsh --profile web --dump-config lists the row that mounts it.

Files it touches

No storage peer appears in the manifest of @tencent-connect/dsh-qqbot, so the dependency line in $DSH_HOME/profiles/<name>/package.json is the only file you can point at; the package description names nothing else.

Removing it

Removing @tencent-connect/dsh-qqbot is the mirror command, dsh plugin --profile web remove @tencent-connect/dsh-qqbot. Its manifest declares no storage peer, so it writes nothing under $DSH_HOME; removing it leaves no files behind.

Common questions

Does it collide with @xmanrui/dsh-im?

@tencent-connect/dsh-qqbot is the one to keep here: It peers dsh-user-approval and @deepseek-ai/dsh-session, so approvals round-trip through the session that will run the tool.

What happens when dsh upgrades?

Nothing declares a version window for @tencent-connect/dsh-qqbot: dsh --version tells you what you are running, and no check will tell you whether @tencent-connect/dsh-qqbot matches it.