feat: add qq-ai-bot (QQ ↔ AI bridge with NapCat + ACP)#5834
feat: add qq-ai-bot (QQ ↔ AI bridge with NapCat + ACP)#5834happysnaker wants to merge 2 commits into
Conversation
Self-hosted QQ ↔ AI bridge for OneBot 11 / NapCat / LLOneBot and ACP-compatible agents. - Opens NapCat WebUI via Umbrel app proxy - Bundles qq-ai-bot bridge service with mock ACP agent - Deterministic password → WebUI token - Auto-generates onebot11.json config on first start - Persistent sessions across restarts - Multi-arch images (amd64 + arm64) Tested with: - NapCat Docker v4.18.7 (verified WebUI at port 6099) - qq-ai-bot v0.1.4 (verified /readyz health endpoint) - Full pre-start hook: config generation + permission fixup
|
Follow-up evidence for the packaged image:
The smoke artifact confirms the |
|
Thanks for the submission @happysnaker, and sorry for the delay on my end! I want to make sure I’m understanding the intended setup flow correctly. It looks like the qq-ai-bot package currently starts the built-in mock ACP agent, and I couldn’t find a user-facing way to configure or connect a real agent without SSH access or modifying the installed Compose file. Is there a supported setup path I’m missing? If so, could you explain how an Umbrel user would go from a fresh install to a working real AI agent? If there isn’t one yet, we’d need that user-facing setup flow before we could move forward with the app. |
2 participants
App Submission: qq-ai-bot
What is qq-ai-bot?
A self-hosted QQ ↔ AI bridge that connects QQ messaging to any ACP-compatible AI agent via OneBot 11. It supports NapCat, LLOneBot, and provides a persistent session-aware bot with streaming progress updates.
linux/amd64,linux/arm64)Package design
/webui)WEBUI_TOKEN)onebot11.jsonin pre-start hook (reverse WS to bot service)${APP_DATA_DIR}Tested
http://<ip>:6099/webui/readyzhealth endpoint respondingScreenshots