# spinabot/brigade

Brigade — Your personal intelligence, built enterprise-grade

Repository: https://github.com/spinabot/brigade
Canonical: https://ross.abutalabs.com/products/brigade
Homepage: https://www.brigade.spinabot.com
Language: TypeScript
License: MIT
License Family: permissive
Topics: agent-runtime, ai, ai-crew, autonomous-agents, brigade, chatgpt, clawdbot, codex, crustacean, hermes, hermes-agent, llm, moltbot, molty, multi-agent, openclaw, self-improving-ai, brigade-agent, pride-of-agents, spinabot
Last push: 2026-08-22T21:10:27+00:00

## Health v2 (maintenance only)
Score: 76/100 (v2, computed 2026-09-03T02:39:23.370411+00:00)
- activity 99, release rhythm 87, longevity 5
- inputs: {"age_days": 75, "days_push": 11, "days_rel": 11, "gap_med": 0, "n_releases_24m": 66}
- flags: young
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 3119, forks 39 (observed 2026-08-28T04:07:44.121163+00:00)

## What it is
Brigade is a self-hosted, MIT-licensed multi-agent runtime where a crew of AI agents on an org chart delegate work, switch models mid-task, and share a long-term memory store (Tideline). It ships as a single Node.js binary that runs a long-lived gateway holding all state, with thin clients (TUI, messaging channels like WhatsApp, MCP memory server) attaching over WebSocket.

## Use cases
- run a crew of autonomous AI agents on my own machine
- self-hosted multi-agent orchestration with shared memory
- personal AI assistant that runs locally without an account
- connect AI agents to WhatsApp and other messaging channels
- schedule recurring agent tasks with cron
- expose my local agent gateway securely to the internet
- benchmark my agent crew against real traffic

## When to choose
- you want a single-operator, self-hosted agent crew with persistent shared memory and no SaaS middleman
- you want one binary that runs as a gateway with thin reconnectable clients
- you want to reuse existing Claude, ChatGPT, or Copilot logins instead of juggling API keys
- you need messaging-channel integrations, cron scheduling, and MCP support out of the box

## When to avoid
- you need a multi-user, team-facing agent platform with per-user auth
- you want a managed cloud service with zero local setup
- you need a framework library to embed agents in your own application rather than a standalone application
- you require formal enterprise compliance certifications or SLAs

## Facets
- artifact type: application
- maturity: active
- function: agent-framework, chatbot, llm-inference, mcp, scheduling, chat-interface, cli
- domain: artificial-intelligence, large-language-models, self-hosted, developer-tools
- platform: windows, cli, self-hosted, cross-platform
- tags: multi-agent, org-chart, shared-memory, gateway-architecture, tui, messaging-channels, whatsapp, local-first, single-operator, benchmarking, ai-agents, automation, macos, linux, nodejs

## Member repositories
- spinabot/brigade (main) score 76

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:07:44.121163+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T07:26:38.074276+00:00, confidence not recorded.
  - readme: https://github.com/spinabot/brigade (fetched 2026-08-28T04:07:44.121163+00:00, sha ec101443b28a)
  - homepage: https://www.brigade.spinabot.com (fetched 2026-08-29T09:41:51.590963+00:00, sha d81a33708607)
  - site_page: https://brigade.spinabot.com/docs (fetched 2026-08-29T09:41:51.600280+00:00, sha 172edebdd330)
  - site_page: https://brigade.spinabot.com/docs/installation (fetched 2026-08-29T09:41:51.602219+00:00, sha e5a70be89d0d)
- Data as of 2026-08-30T08:39:29.467469+00:00.