DSH plugin that drives a normal QQ account through NapCat / OneBot v11 with persona, mood, per-person memory, image and Bilibili video understanding, group moderation and a token-protected web console — deny-all by default until you fill in an allowlist.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-11-18
License
NOASSERTION
01What can it help you accomplish?
Let a plain QQ account reply in groups and private chats with a persona and memory
Short, persona-driven replies with mood, plus per-person long-term memory and session summaries that carry over after a context rotation
People who want their own QQ number to feel like a person in a group instead of deploying an official bot account
Understand images and Bilibili videos before replying to them
Replies grounded in the picture, or in a video's subtitles, frames, danmaku and top comments; the viewing happens in a temporary session so only a summary stays in the main thread
Group members who paste screenshots and video links and expect a real reaction rather than "I can't open links"
Moderate a group and keep an eye on the bot from one web console
Auto-recall plus mute when a word list hits, group management, reminders, and a console covering sessions, memory, contacts, viewing history, config and logs
Group owners running the bot on a server who need moderation and operational visibility without SSH-ing into logs
02How to install into DeepSeek Harness
Prerequisites
- DeepSeek Harness that already answers normally (a default model is configured) — the README lists this first
- A spare QQ account
- NapCat or another OneBot v11 implementation with a WebSocket server
- `ffmpeg` on the local PATH if you want per-frame video analysis
Installation steps
- 01
`dsh plugin add qfish` (or `pnpm add git+https://github.com/hyun20202023-ui/dsh-qfish.git`), then restart DSH
$ dsh plugin add qfish
- 02
Install NapCat and log in the QQ account, then create a WebSocket server on port 3001 with message format `array`
- 03
In DSH → 插件设置 → qfish set `url` to `ws://127.0.0.1:3001`, keep `consolePort` at `8090`, and set `consoleListen` to `0.0.0.0` if you run on a server
- 04
Choose an access mode: allowlist (`userAccessMode: allowlist` plus `userIds`, `groupAccessMode: allowlist` plus `groupIds`) or fully open (`blocklist` with empty lists)
- 05
Log in to QQ by scanning the QR code in NapCat or in the console's 行为参数 tab
- 06
Open the console at `http://<address>:8090/?t=<token>` — the token is `consoleToken`, or the auto-generated one in `<profile>/onebot-data/console-token.txt`
Verify the integration
- The console status shows `napcat` as true
- Mention the bot in an enabled group and it replies; for private chat set `respondToPrivate: true` and put your QQ number in `userIds` first
- The DSH startup log contains the line 「控制台已启动:http://…」 with the full token-bearing URL
03DSH integration and capability boundaries
A DSH plugin bundle that connects to NapCat over OneBot v11 WebSocket: the bot runs on DSH's own models, sessions and tools, and the same package also ships a token-protected web console and a floating button in the DSH page.
Persona, mood and language imitation
a markdown persona file, the group's recent messages, and word lists (slang, banned words, memes)→short replies split by tone rather than character count, with mood and affection affecting length, emoji and memory tone
writes mood and affection state to `mood.json` and slang lists to `slang.json` / `slang-normal.json`Memory and session rotation
each person's chat history in groups and private chats→per-person memory that compresses when full, session summaries that travel into the next session, and a group cache so the bot can pick up the thread
writes `memories.json`, `summaries.json` and `state.json` in the profile data directoryprivate-chat rotation also writes a memory entry; group rotation does notGroup moderation
five word lists plus a master switch→automatic recall and mute on a hit, with a mute-free tier available
recalls messages and mutes members in the connected QQ groupImage and Bilibili video understanding
an image sent to the chat, or a Bilibili video link→a reply based on the picture, or on subtitles, frames, danmaku and top comments; overly long videos are declined honestly
needs `ffmpeg` for per-frame frames; writes a nine-grid frame cache under `frames/`writes `bili-memory.json` and `video-notes.json` viewing recordsWeb console
a browser request carrying the console token→sessions, memory, contacts, viewing history, config and logs in one page, plus behaviour tuning such as reply count and video limits
serves HTTP on `consolePort` (default 8090), bound to `consoleListen`a floating button in the DSH page opens the same consoleContent tools and operations
requests from the model during a conversation→image search, web search and page text, Bilibili cards, NetEase / QQ Music cards, reminders, cross-group messages and `/dsh` server commands
sends messages into other groups or private chats`/dsh` runs server commands and is restricted to backend permissions
04Who is it for? When not to use it?
Good for
- People who want their own QQ number to feel like a person in a group instead of deploying an official bot account
- Group members who paste screenshots and video links and expect a real reaction rather than "I can't open links"
- Group owners running the bot on a server who need moderation and operational visibility without SSH-ing into logs
Not for
- Default deny: after install the bot replies to nobody. You must fill in a QQ user / group allowlist — an empty list means everything is refused. Fully opening it means switching both access modes to `blocklist` with empty lists.
- It cannot be installed alongside `dsh-onebot`: both register `/onebot/api` and fight over the same NapCat connection. The project is a derivative of `dsh-onebot@1.4.0` (MPL-2.0) and the related code stays under MPL-2.0.
- The console needs a reachable port and a token. On a server you must change `consoleListen` from `127.0.0.1` to `0.0.0.0` and open port 8090 (plus 6099 for NapCat's web UI); port 3001 should stay local to the plugin.
- The protocol side can be rate-limited: qfish goes through OneBot / NapCat with a normal QQ account, and the README's own comparison table says the protocol endpoint may hit risk control. The same QQ number also cannot be logged in from two machines — two NapCats will kick each other.
05Compatibility, maintenance and safety notes
- Default deny: after install the bot replies to nobody. You must fill in a QQ user / group allowlist — an empty list means everything is refused. Fully opening it means switching both access modes to `blocklist` with empty lists.
- It cannot be installed alongside `dsh-onebot`: both register `/onebot/api` and fight over the same NapCat connection. The project is a derivative of `dsh-onebot@1.4.0` (MPL-2.0) and the related code stays under MPL-2.0.
- The console needs a reachable port and a token. On a server you must change `consoleListen` from `127.0.0.1` to `0.0.0.0` and open port 8090 (plus 6099 for NapCat's web UI); port 3001 should stay local to the plugin.
- The protocol side can be rate-limited: qfish goes through OneBot / NapCat with a normal QQ account, and the README's own comparison table says the protocol endpoint may hit risk control. The same QQ number also cannot be logged in from two machines — two NapCats will kick each other.
NOASSERTION(README 注明由 dsh-onebot@1.4.0 二次开发,相关代码继续适用 MPL-2.0) · README 分支 main · 最新 release v0.3.31 (2026-11-13)
06Frequently asked questions
Why does the bot ignore every message right after install?
That is the default. qfish ships deny-all: an empty allowlist refuses everyone. Set `userAccessMode: allowlist` with your QQ number in `userIds`, and `groupAccessMode: allowlist` with the group numbers in `groupIds` — or switch both to `blocklist` with empty lists to open it up. Private chat additionally needs `respondToPrivate: true`.
What has to be running outside DSH?
NapCat (or another OneBot v11 implementation) with a WebSocket server. Locally, create one on port 3001 with message format `array`; on a server, run the `mlikiowa/napcat-docker` image with ports 3001 and 6099 published, then scan the QR code at `http://<server>:6099` to log in the QQ account. `ffmpeg` on the PATH is only needed for per-frame video frames.
The QQ account is online but every turn is blocked — what now?
DSH may have archived qfish's sessions, and archived sessions are refused before the model ever runs. Quit DSH, edit `~/.dsh/storages/workspace.json`, delete every `archivedSessionIds` entry that starts with `onebot:`, and start DSH again. If the console chat box stays idle instead, the profile is probably missing a default model, so add an `agent-default-model` block to `cordis.patch.yml`.
How do I get into the web console?
The console is an HTTP page that requires a token: `http://<address>:8090/?t=<token>`. The token is `consoleToken` from the config, or the auto-generated value in `<profile>/onebot-data/console-token.txt`, or the full URL printed in the DSH startup log line 「控制台已启动:http://…」. On a server you must first set `consoleListen` to `0.0.0.0` and open port 8090.
Can it run next to dsh-onebot?
No. qfish is a derivative of `dsh-onebot@1.4.0` and both register `/onebot/api` and compete for the same NapCat connection, so installing both breaks the connection. Related code stays under MPL-2.0.
07Related DSH workflows
dsh-im
by xmanrui
把 IM 机器人接入 DSH:统一管理飞书/微信/钉钉/企业微信/QQ/Telegram/Discord/WhatsApp 八个渠道,扫码或凭据接入、流式回复与设置页管理
dsh-aurabot-qq
by aureth-labs
Connects DSH sessions to QQ through OneBot v11 and exposes configurable chat, media, memory, and social tools.
dsh-qqbot
by tencent-connect
Official QQ Bot IM channel plugin for dsh: QQ WebSocket transport, QR扫码 credential binding, per-peer isolated agents, Markdown chunked replies, slash commands, preset mounting
dsh-wechat
by xcisxc29
WeChat channel for DeepSeek Harness
08Data and sources
> qfish 是 DeepSeek Harness 的 QQ 插件。用 NapCat / OneBot 接普通 QQ 号,不需要申请官方机器人。
- **直连 DSH**:模型、会话、工具都走 DSH,中间没有别的层
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-11-18. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.
