Plugins

Five DSH utilities in one plugin: drive existing sessions over QQ (needs an OneBot 11 implementation such as NapCat running alongside), ask another session a question with a context guard, pause the running turn, restart DSH on Windows with optional auto-resume (via the install-restart.ps1 scheduled task), and inject peak-hour token discipline.

Connect DSH to a local BiliMemory backend for Bilibili search, collection, status and login tasks, A-Memorix shared memory health checks, plus QQ link status, QQ user allowlists and QQ watcher restart. The repository includes a Windows one-click installer that installs or repairs MaiBot A-Memorix when missing, then configures local-bge-small-zh, embedding and shared memory. It also provides install-memory.cmd for memory-only repair. Requires Windows, DSH Desktop 0.2.1-rc.2+, Node.js 22.19+, Python 3.12, Playwright/Edge, FFmpeg, a running BiliMemory API at 127.0.0.1:8765, a local embedding service at 127.0.0.1:11435, a Bilibili login, and MaiBot/NapCat for QQ. Voice, RVC and cover features are excluded.

Bridge QQ (via NapCat) into DeepSeek Harness, turning private and group chats into session prompts and sending replies back to QQ.

Keeps the NapCat QQ backend alive next to DSH: probes the OneBot 11 HTTP port at startup, launches NapCat when the port does not answer, then rechecks every 45 seconds, kills duplicate process chains, hides the console window, can create a logon scheduled task when a task name is set, and adds a settings page plus napcat_status, napcat_restart and napcat_dedupe tools. Optionally remembers the QQ password, behind a risk confirmation, so an expired fast-login token can be renewed without scanning a QR code. Windows only; without that scheduled task the launched QQ exits together with DSH.

Windows NapCat deployment guide and read-only loopback port checks for DSH, with a user-initiated administrator launcher.

Bridges a OneBot QQ bot into DSH: the owner's direct messages open a session on the same home, answers go back to QQ, and files named with \[SEND_FILE: path] are delivered. Needs a OneBot v11 implementation with a forward WebSocket (such as NapCat) and ownerId set in the config, otherwise every message is ignored. The home it shares with the main session is provided by the separately installed dsh-wakeup plugin. It also runs an unauthenticated local status endpoint on 127.0.0.1:3002 with open CORS that returns the owner QQ number, the login QR code and recent log lines (including the first 60 characters of incoming messages).