Brigade

简介

<p align="center"> <img src="docs/assets/brigade-wordmark.svg" alt="Brigade (by Escoffier Labs)" width="640"> </p>

<p align="center"> <strong>Run agents anywhere. Keep one record of the work.</strong><br> Brigade tracks what's ready, who claimed it, and what ran across Claude Code, Codex, cloud agents, and your machines. Your local harnesses stay in sync on MCP servers, skills, and memory. </p>

<p align="center"> <a href="https://brigade.tools/docs/getting-started/install">Install</a> · <a href="https://brigade.tools/docs">Docs</a> · <a href="docs/comparison.md">Compare</a> · <a href="QUICKSTART.md">Quickstart</a> </p>

<p align="center"> <img src="https://shieldcn.dev/github/ci/escoffier-labs/brigade.svg?workflow=ci.yml&branch=main&label=ci&size=xs" alt="CI status"> <img src="https://shieldcn.dev/pypi/v/brigade-cli.svg?label=pypi&size=xs" alt="PyPI version"> <img src="https://shieldcn.dev/https/raw.githubusercontent.com/escoffier-labs/brigade/download-metrics/downloads.json.svg?size=xs" alt="Combined PyPI and npm downloads per month"> <img src="https://shieldcn.dev/badge/python-3.10+-blue.svg?logo=python&logoColor=white&size=xs" alt="Python 3.10+"> <img src="https://shieldcn.dev/badge/rust-code_graph-b7410e.svg?logo=rust&logoColor=white&size=xs" alt="Rust: code graph engine"> <img src="https://shieldcn.dev/badge/go-evidence_log-00add8.svg?logo=go&logoColor=white&size=xs" alt="Go: evidence log engine"> <img src="https://shieldcn.dev/badge/license-MIT-4e7247.svg?size=xs" alt="MIT license"> </p>

Coding work now runs in several places at once. You drive Claude Code or Codex in a terminal, a background run works another repo, a cloud agent opens a pull request in another tab, and CI checks the result somewhere else. Each tool keeps its own history. When one agent hands work to the next, the handoff is usually a sentence like "tests pass."

Agents did not create this split. Terminals, background jobs, and remote machines have always kept separate records. Running agents in parallel makes each gap cost more.

Brigade keeps one record around the work itself, across harnesses, repos, machines, and cloud seats: which tasks are ready, who claimed them, which commands ran and how they exited, and what the next session should know. It also keeps MCP servers, skills, and memory in sync, so an agent picking up the work in another harness starts with the same setup and context. The record is plain local files, with an optional hub for claims across machines. Agents read and write it through the CLI and MCP. You set policy, budgets, scopes, and gates, and can stop the work at any point.

For example, a Claude Code agent can hand a verify receipt to Codex in an evidence package, alongside a handoff that explains the change. Codex checks the package and the receipt's real exit code instead of taking the agent's word for it.

The Python CLI may send a passive version request. Python CLI telemetry lists its fields, retention, and opt-outs.

Stable: v0.30.0 (brigade-cli==0.30.0 on PyPI, @escoffier-labs/brigade@0.30.0 on npm). Beta: main is the 0.31 preview line (0.31.0.devYYYYMMDD wheels). See the changelog for what each release changed.

The downloads badge sums brigade-cli on PyPI (excluding mirrors) and @escoffier-labs/brigade on npm over the same 30 completed UTC days. Downloads include automation and do not count unique people. The metric JSON records each source, the period, and the last successful refresh. npm platform companions are excluded. Daily refreshes retain the previous metric if a source fails validation or its latest day is more than three UTC days old.