brigade vs OpenDots
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 — CopilotKit template for always-on AI coworkers ('Dots'): each gets a role, tools and its own computer, works in chat, calls and Slack, and saves approved drafts into editable Spaces.
Both run a self-hosted crew of role-specialised agents reachable from chat apps like Slack, with app connectors. Brigade centres on org-chart delegation and shared memory; OpenDots on per-Dot computers and reviewed pages.
| brigade | OpenDots | |
|---|---|---|
| Stars | 11k | 6.4k |
| Forks | 81 | 940 |
| Language | TypeScript | TypeScript |
| License | MIT | MIT |
| Last activity | 2 days ago | yesterday |
| Topics | agents, orchestration | agents, orchestration |
| Curated connections | 5 | 5 |
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.
OpenDots — the curator's take
Use it as a starting point for a self-hosted agent workspace where specialist agents share a document library with humans — per-Dot permissions, approve-before-run cards for MCP tools, and an optional persistent browser/terminal per Dot. NOT a hosted product or a plain library: alpha, you run the infrastructure, and conversations need CopilotKit Intelligence (hosted, local Docker eval, or a licensed self-host) — a real dependency to weigh. Want only the governed computer per agent? Take OpenBot.