docs: add qq-ai-bot to community resources and integration guide#132
Merged
Conversation
happysnaker
force-pushed
the
add-qq-ai-bot-community
branch
from
July 2, 2026 08:35
7c57952 to
17653d9
Compare
Contributor
Author
|
Small maintainer note: this entry is intentionally framed as a runnable bot scaffold rather than another low-level SDK. The point is to give NapCat users one concrete path from NapCat / OneBot transport to an ACP-compatible local agent, with persistent sessions, progress streaming, and a public Docker demo they can actually deploy. |
13 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
qq-ai-botto the NapCat community resources pageqq-ai-botsection to the integration guideWhy
qq-ai-botis relevant for the NapCat ecosystem because it gives developers a deployment-oriented TypeScript starting point for NapCat-connected AI bot workflows rather than another low-level SDK entry.The integration section also makes the exact reverse-WS wiring path explicit for users who want to connect NapCat to an ACP-compatible local agent.