StackMap
Subscribe

brigade vs Octop

Self-hosted crew of AI agents on an org chart sharing one long-term memory: delegation, mid-task model switching, 1,000+ app connectors, reachable from terminal, WhatsApp, Telegram or Slack. — versus — 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.

The curated verdict

Both give a group a self-hosted crew of AI agents sharing long-term memory, reachable from chat apps. Brigade organises agents on an org chart with 1,000+ app connectors; Octop centres on per-user expert switching and China-market IM channels.

brigadeOctop
Stars11k12k
Forks811.6k
LanguageTypeScriptPython
LicenseMITMIT
Last activity2 days agoyesterday
Topicsagents, orchestrationagents, orchestration
Curated connections54

brigade — the curator's take

For one owner who wants a personal multi-agent assistant they host themselves — reuses your Claude/ChatGPT/Copilot sign-in, approval-gated privileged actions, no telemetry. The README is heavy on vibes (the 'Bloody Benchmark' is a public tunnel, not a benchmark), so judge the code, not the copy. One lean agent on a $5 VPS? picobot is simpler. Company-scale fleets with budgets and governance? paperclip.

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.