Skip to content

docs: add qq-ai-bot to messaging clients#1592

Merged
benbrandt merged 1 commit into
agentclientprotocol:mainfrom
happysnaker:docs/add-qq-ai-bot-client
Jul 6, 2026
Merged

docs: add qq-ai-bot to messaging clients#1592
benbrandt merged 1 commit into
agentclientprotocol:mainfrom
happysnaker:docs/add-qq-ai-bot-client

Conversation

@happysnaker

Copy link
Copy Markdown
Contributor

Summary

  • add qq-ai-bot to the Messaging section of ACP clients docs

Why

qq-ai-bot is a public ACP-compatible messaging client surface for QQ / OneBot 11 deployments. It sits alongside the other messaging-oriented ACP clients already listed on this page.

Repo details:

Positioning in one line:

  • self-hosted bridge for OneBot 11 / NapCat / LLOneBot that connects QQ messaging to ACP-compatible agents with persistent sessions and progress streaming

Scope

  • docs-only change in docs/get-started/clients.mdx

@happysnaker
happysnaker requested a review from a team as a code owner July 3, 2026 00:29
@happysnaker

Copy link
Copy Markdown
Contributor Author

Small maintainer note: this entry is intentionally proposed under Messaging clients, not as another editor / IDE integration. qq-ai-bot is a runnable QQ / OneBot transport surface that bridges into ACP-compatible agents with persistent sessions, progress streaming, and a public Docker demo, so the main value is showing one concrete non-editor ACP client shape that people can actually deploy.

@happysnaker

Copy link
Copy Markdown
Contributor Author

Small follow-up note: the public Docker image for qq-ai-bot now ships both linux/amd64 and linux/arm64, which makes this messaging client entry a bit stronger for self-hosted ACP users on ARM NAS / SBC / homelab hardware as well, not only x86 hosts.

@benbrandt
benbrandt enabled auto-merge (squash) July 6, 2026 11:42
@benbrandt
benbrandt merged commit ddbf27d into agentclientprotocol:main Jul 6, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants