[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f1qidstwjt09xd":3},{"code":4,"message":5,"data":6,"timestamp":31},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":16,"summary_md":17,"topic":18,"github_topics":21,"license":27,"homepage":28,"updated_at":29,"history":30},"NapNeko\u002FNapCatQQ",17,"Modern protocol-side framework based on NTQQ","TypeScript",11514,838,479,943,[],"A OneBot 11 protocol bridge on NTQQ for developers building QQ chat bots in TypeScript or other languages.","NapCatQQ is a protocol-side framework that exposes QQ messaging through the OneBot 11 standard, aimed at developers who want to build bots on top of a real QQ client rather than reimplement the protocol. It is not a bot framework itself; it is the adapter that sits between QQ and your bot code.\n\n## The problem\n\nYou want to automate a QQ group or private chat: respond to commands, push notifications, or connect an LLM bot. Before a project like this, you either reverse-engineered QQ's internal protocol or depended on unofficial libraries that broke with client updates. NapCatQQ runs alongside NTQQ and translates incoming messages and outgoing calls into OneBot 11 events and API actions. After setup, your bot code can send and receive QQ messages without handling QQ's native protocol directly.\n\n## What's different\n\nNapCatQQ's core value is that it works at the protocol side of NTQQ rather than using screen automation or an entirely different client. The README states it implements most standard OneBot 11 interfaces, so existing bots written for that standard can connect with relatively few changes. Running on NTQQ also means the project tracks a real QQ client's behavior rather than a from-scratch protocol implementation. The trade-off is that NapCat is only the protocol layer: you still need a bot framework or your own event loop to decide what to reply. The README also points to SnowLuma as a GUI replacement for NapCat, implying that GUI management is not the core of this repository.\n\n## Who should try it\n\nThis fits developers who already have a QQ bot idea and are comfortable running a local service and editing configuration. If you use a bot framework compatible with OneBot 11, or you are willing to write an HTTP\u002FWebSocket client, NapCat removes the hardest part of talking to QQ. It is a poor fit if you expect a ready-made bot with plugins and a web dashboard; this project supplies the protocol adapter, not the bot logic. The README notes that setup questions, integration issues, and underlying framework problems are not answered by the community, so self-reliance matters from the start.\n\n## Requirements and limitations\n\nThe README directs first-time users to the documentation before anything else, and the project is non-profit with community support limited to what users can search for themselves. That means installation and configuration are your responsibility, and the community channels are not a help desk for basic setup problems. The license is described as mixed: third-party code keeps its original license, some parts are used under separate authorization, and the remaining logic follows the repository's own license. The README explicitly forbids developing another project based on NapCat code without the author's authorization, which rules out certain derivative or commercial reuse. It also frames the project as improving ease of use for message-push scenarios, so check that your intended use fits that scope and local regulations.\n\n## HotRepo's take\n\nHotRepo's only dated signal for NapCatQQ is a weekly TypeScript board observation on 2026-10-25: +479 stars that week, rank #17. There is no daily-board history in the stored coverage, so whether this interest persists cannot be judged from that single sample. The repository is 943 days old, which gives some context for age but not for current maintenance quality. Before adopting, verify that your bot framework's OneBot 11 compatibility matches the interfaces NapCat documents, since that integration detail matters more than the star count.\n\n[Project source and documentation](https:\u002F\u002Fgithub.com\u002FNapNeko\u002FNapCatQQ)",{"slug":19,"name":20},"developer-tools","Developer Tools",[22,23,24,25,26],"napcat","ncqq","ntqq","onebot","onebot11","NOASSERTION","https:\u002F\u002Fnapneko.github.io","2026-10-25T12:17:15Z",[],1792969025]