You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Activity
happysnaker commentedon 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 agentshape without needing extra third-party runtime setup up front.