[GH-ISSUE #780] Proposal: add a NapCat + OneBot + ACP agent Docker Compose sample #22959

Open
opened 2026-08-20 21:54:28 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @happysnaker on GitHub (Jul 2, 2026).
Original GitHub issue: https://github.com/docker/awesome-compose/issues/780

Summary

I would like to propose a new Docker Compose sample for a messaging-native AI stack:

  • NapCat for QQ / OneBot transport
  • qq-ai-bot as the OneBot 11 ↔ ACP bridge
  • a tiny mock ACP agent for deterministic first-run validation

Why this sample could be useful

Most Compose examples around AI currently focus on web UIs or local model serving. This sample would instead show a reproducible message-channel deployment path: a user can validate QQ -> OneBot -> bot bridge -> agent runtime as one stack, then swap the mock agent for their own runtime later.

I think this fits the repo goal because it is still a local-development / tinkering sample, but demonstrates multi-service Compose orchestration for a real integration shape instead of a single UI.

Proposed structure

  • compose.yaml for NapCat + qq-ai-bot + mock ACP agent
  • sample README with startup / token / WebUI notes
  • clear note that it is not production-ready and mainly for local validation

If this direction sounds useful, I can prepare the actual sample PR next.

Reference project:

Originally created by @happysnaker on GitHub (Jul 2, 2026). Original GitHub issue: https://github.com/docker/awesome-compose/issues/780 ## Summary I would like to propose a new Docker Compose sample for a messaging-native AI stack: - **NapCat** for QQ / OneBot transport - **qq-ai-bot** as the OneBot 11 ↔ ACP bridge - a tiny **mock ACP agent** for deterministic first-run validation ## Why this sample could be useful Most Compose examples around AI currently focus on web UIs or local model serving. This sample would instead show a reproducible **message-channel deployment path**: a user can validate `QQ -> OneBot -> bot bridge -> agent runtime` as one stack, then swap the mock agent for their own runtime later. I think this fits the repo goal because it is still a local-development / tinkering sample, but demonstrates multi-service Compose orchestration for a real integration shape instead of a single UI. ## Proposed structure - `compose.yaml` for NapCat + qq-ai-bot + mock ACP agent - sample README with startup / token / WebUI notes - clear note that it is **not production-ready** and mainly for local validation If this direction sounds useful, I can prepare the actual sample PR next. Reference project: - https://github.com/happysnaker/qq-ai-bot
Author
Owner

@happysnaker commented on GitHub (Jul 3, 2026):

Actual sample is now ready here: #781\n\nThis keeps the scope intentionally local/tinkering-friendly and uses the built-in mock ACP agent first, so reviewers can validate the QQ -> NapCat / OneBot 11 -> qq-ai-bot -> ACP-compatible agent shape without needing extra third-party runtime setup up front.

<!-- gh-comment-id:4871959263 --> @happysnaker commented on GitHub (Jul 3, 2026): Actual sample is now ready here: #781\n\nThis keeps the scope intentionally local/tinkering-friendly and uses the built-in mock ACP agent first, so reviewers can validate the `QQ -> NapCat / OneBot 11 -> qq-ai-bot -> ACP-compatible agent` shape without needing extra third-party runtime setup up front.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-compose#22959