Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

【开源自荐】qq-ai-bot:OneBot 11 + ACP 的 QQ ↔ AI 自托管脚手架

Open
#118 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Quiet
Tech stack
docker
Domain
content

Research direction

This issue is a project recommendation for the OpenGithubs/weekly repository, not an implementation request. No repository file, test, or entry point is named, so first identify how weekly project submissions are recorded and what editorial criteria apply. Done would require a maintainer-approved update to the appropriate weekly content.

Written by the indexing model from the issue text.

Description

项目名称

qq-ai-bot

项目地址

https://github.com/happysnaker/qq-ai-bot

在线阅读

https://happysnaker.github.io/qq-ai-bot/

项目简介

qq-ai-bot 是一个把 QQ / OneBot 11 接到 本地 AI agent 的自托管脚手架。前面兼容 NapCat / LLOneBot,后面接 ACP-compatible agent。它重点不是做一个新的聊天 UI,而是把消息入口、会话状态、进度回传、Docker 演示和部署文档整理成一个可以直接跑起来的 QQ ↔ AI bot 基础设施仓库。

推荐原因

  • 支持 OneBot 11 / NapCat / LLOneBot + ACP agent,定位更偏 bot 基础设施,而不是玩具聊天机器人。
  • 仓库自带 NapCat + qq-ai-bot + mock ACP agent 的最小 Docker demo,可以先验证完整链路,再替换成自己的 agent。
  • 有 persistent sessions、progress streaming、轻量入站去重、correlation ID、/metrics、/readyz 这类更偏工程化的能力。
  • 文档比较完整:项目介绍、特性、快速开始、Docker demo、FAQ、部署矩阵、架构说明、Roadmap、Contributing、Security 都补齐了。
  • 已进入 OneBot 生态页,更像一个可复用的集成层 / 接线层项目。

适合分类

AI 开源项目 / 机器人基础设施 / 自托管 / 工程化部署

License

MIT

Dominant language
No language data
Stars
1.7k
Forks
72
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenGithubs/weekly

All issues in OpenGithubs/weekly

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.