DandanLLab/SnowCatQQ

What it does

SnowCat is a community-maintained third-party QQ client built by merging two upstream projects: NapCat (the OneBot implementation) and SnowLuma (extra actions). It injects a single-file bundle into the official QQ 9.9.37-54395 x64 process through a winmm.dll proxy that hooks v8::ScriptCompiler, so the official install stays unmodified while the client exposes OneBot v11 (forward/reverse WebSocket, HTTP, HTTP SSE), MCP over Streamable HTTP at /mcp, and 56 additional actions covering QZone, group albums, check-ins, flash images and more SnowCat repository. A React-based WebUI runs on port 6099.

The target audience is individual developers running self-hosted QQ bots or companion agents. The README explicitly positions this as a personal-developer route, separate from Tencent's audited official bot platform official bot platform. The repository is structured as 26 TypeScript packages plus PowerShell release tools; the V8 channel source and compiled DLL are both included, and the project also publishes a portable-environment builder repository structure.

Quick start

Requirements: Windows x64 and the official QQ 9.9.37-54395 installer. From the repository root in PowerShell:

1. Unpack the official installer into a portable layout:

   ./release-tools/snowcat-qq-unpack.ps1 -Installer QQ_9.9.37_261103_x64_01.exe
   

2. Deploy the V8 channel, launch QQ and run a 45-second health check:

   ./release-tools/build/snowcat-run.ps1
   

3. Open the WebUI at http://127.0.0.1:6099/webui/ quick start.

Once running, point an OneBot v11 client at the exposed endpoint, or connect an MCP client to /mcp to call all actions as tools. Prebuilt releases are available on the releases page. The repo also lists companion dsh plugins (channel, team-group, life-engine) for wiring the client into an agent sandbox dsh-channel-qq.

Constraints and risks

• Windows x64 only, tied to the exact QQ build 9.9.37-54395; a new QQ release will likely require offset-table and channel updates.
• Using a third-party client on your own QQ account carries account-risk the README itself acknowledges; it does not guarantee account safety account security note.
• The mechanism relies on injecting a proxy DLL into the official process, which may trigger antivirus or platform-side risk controls.
• The license badge says MIT, but GitHub reports the license as unrecognized (NOASSERTION), so verify the actual license file before redistribution.
• The README is dominated by a long manifesto; implementation details live in the separate docs (V8 channel writeup and architecture audit) V8 channel doc architecture audit.

HotRepo's take

The project appeared on HotRepo's new-project JavaScript list on 2026-11-12, gaining 103 stars and 54 forks within roughly eight hours of its recorded growth window — a fast initial response for a project created just one day earlier. That burst coincides with the stated retirement of NapCat and disappearance of SnowLuma, so the attention is plausibly continuity-driven rather than independent adoption. With no GitHub daily rank recorded and only a single snapshot, there is not yet enough same-metric history to judge whether the interest sustains. The technical claim worth watching is whether the 26-package TypeScript source and the checked-in V8 channel DLL stay aligned with future QQ builds.