Octop vs qm
Tencent Cloud's self-hosted, multi-user AI assistant: per-user expert agents, AgentTeams, memory, RAG and connectors, served as one process to a web dashboard, CLI and 8+ IM channels. — versus — Multiplayer agent harness for startups: every employee gets a scoped workspace — memory, files, keychain, crons, sandbox — in Slack and web, with Pi/OpenCode/Codex/Claude Code swappable underneath.
Same multi-user shape — every person gets a scoped workspace with memory and files. qm targets startup teams in Slack with swappable coding harnesses underneath; Octop targets households and small teams across web, desktop and Chinese IM.
| Octop | qm | |
|---|---|---|
| Stars | 12k | 16k |
| Forks | 1.6k | 1.9k |
| Language | Python | TypeScript |
| License | MIT | MIT |
| Last activity | yesterday | yesterday |
| Topics | agents, orchestration | agents, orchestration |
| Curated connections | 4 | 9 |
Octop — the curator's take
Built for a household or small team that wants one box everyone talks to: JWT-isolated users, an expert library to switch specialists per task, and reach through Feishu, DingTalk, QQ, WeChat, WeCom, Telegram or Discord without wiring each bot. Strongest fit inside the China IM/Tencent ecosystem (Docs, Meeting connectors); the extras — browser sessions, remote desktop, ACP delegation to Claude Code/OpenCode — make it a personal ops console, not just chat. Skip it if you want a library to build agents with (it is a product), if you only need one user on one channel (a single-binary bot is lighter), or if beta AgentTeams orchestration is your main reason to adopt.
qm — the curator's take
The org-level answer to "give everyone at the company an agent": per-person and per-channel scopes keep memory, credentials and files isolated, and the harness underneath (Pi, OpenCode, Codex, Claude Code) is swappable, so the deployment isn't a bet on one vendor. Security postures (strict/auto/dangerous) plus a hard command-deny policy that survives even Dangerous mode are unusually well thought through. NOT for individuals — this is Postgres + sandbox + deployment-repo infrastructure; a solo dev should run a harness directly. Quirk: contributions are accepted as prose ADRs, not code PRs.