This release is a pre-release and may not be stable for production use.
One shared record for every coding agent you run: ready work, safe claims, proof that checks passed, and memory that carries over between tools.
Install · Docs · Compare · Quickstart
Brigade lets coding agents work autonomously across repos, machines, and cloud seats while the operator stays in control. You set policy, budgets, scopes, and gates, and can inspect or stop the work. Agents leave a record of what they did: verification receipts with real exit codes, run journals, claims, and lineage. 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 can check the package and receipt instead of trusting a sentence that says "tests pass."
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.
What it does
- Ready work and safe claims.
brigade work readylists unblocked tasks. Claims are atomic, so two agents cannot take the same item. - Evidence between agents. A check run through Brigade records the command, the real exit code, and the Git state. The next agent can inspect the receipt or verify an exported evidence package. Handoffs link that evidence to the work that remains.
- Shared memory with an owner. Agents write handoffs with evidence sections. The memory owner lints and files them under the ingest policy. Safe notes can auto-file, and ambiguous notes enter a review queue. Session-start recall is capped.
- One tool catalog across harnesses. MCP servers, tools, and skills are defined once. Projection plans preview each harness's config before sync writes it.
- Cloud agents tracked next to local ones. Tasks you hand to Codex Cloud, Cursor cloud agents, or Jules are registered with their provider task ID and reconciled against provider and GitHub state, so they show up beside local runs instead of disappearing into another tab.
- Optional fleet view. A self-hosted hub can arbitrate repo claims across machines and show runs, harness sessions, and cloud tasks on one board.
Learning in Brigade means scoring skills against eligible captured receipts, then promoting or rolling them back. Autonomous memory reflection is planned in #1856.
Examples
Two agents, one backlog. Each agent asks for the next ready task. The second claim on the same item fails with exit 13 and names the holder.
brigade work ready --parallel-safe # ready tasks, grouped into waves that do not touch the same files
brigade work claim --next --actor codex # take the highest-priority ready task
"Tests pass" with a receipt. The agent runs the check through Brigade instead of reporting it from memory.
brigade work verify run --target . --command "pytest -q"
The receipt keeps the command, exit code, Git commit, and dirty state, so a reviewer can check the claim without rerunning it.
Switching harnesses mid-task. Claude Code ends a session with a handoff. The next Codex session starts from the brief instead of a blank context.
brigade handoff lint # check the handoff before it is filed
brigade work brief --target . # what the next agent sees at session start
One MCP config for every tool.
brigade mcp plan # read-only preview
brigade mcp sync --write # merge into each harness's native config
Install
If Node.js 22 or newer and npm are installed on glibc Linux x64/ARM64, macOS x64/ARM64, or Windows x64, install the npm package. This route does not need Python or pipx first:
npm install --global @escoffier-labs/brigade@0.30.0
brigade setup
To try it without a global install, run each command through npx instead, for example npx --yes @escoffier-labs/brigade@0.30.0 --version. The package brings its own uv, through platform packages that npm installs as optional dependencies, and the published 0.30.0 wheel. Leave optional dependencies enabled. The first launch downloads a managed Python, so it needs network access. Install Git yourself for repository features. npm targets are Linux (glibc) x64 and ARM64, macOS x64 and ARM64, and Windows x64. Upgrade with npm, because brigade update refuses npm-managed installs. Platform details and known limits: npm package notes.
On other platforms, or to use Python 3.10 or newer directly:
pipx install brigade-cli # or: uv tool install brigade-cli
brigade setup
Then follow the install guide or QUICKSTART.md. To let your coding agent do the setup, hand it first 10 minutes and the agents guide.
If setup fails, run brigade bug report --summary "What happened and what you expected" --dry-run in the affected workspace. Review the complete redacted preview before sharing. See bug reports.
For preview builds on a pipx install, run brigade update --channel beta. Details: update channels.
MCP servers
brigade-cli includes two MCP servers. --stdio runs them over stdin and stdout, and --http serves them on loopback Streamable HTTP for hosts that connect by URL (details).
brigade memory serve-mcp --stdio: memory cards from the repo and user stores, with six tools:list_cards,get_card,search_cards,memory_status,work_brief, andwrite_handoff.write_handoffis the one write tool; it drafts a Memory Handoff and never edits a canonical card (details).brigade skills serve-mcp --stdio: the reviewed skill registry, read-only, with search, read, lint, compatibility, and install-history tools.
Without a global install, uvx --from brigade-cli brigade memory serve-mcp --stdio runs the same server.
How it compares
Most neighbors go deeper on one layer. Brigade connects work, memory, tool config, and evidence around the same coding-agent task. Where a neighbor is stronger, its cell says so. Sources, dated notes, and projects that left these tables: docs/comparison.md (checked 2026-10-18).
Key: 
Work and orchestration
| Project | Ready work | Claim safety | Parallel and run control | Task store | Verification |
|---|---|---|---|---|---|
| Brigade | Ready set + parallel-safe waves |
Fail-closed claims, optional hub |
Waves, campaigns, declared limits |
Local JSON ledger, not a task DB |
Command receipts |
| Beads | Built in |
Atomic claim |
Agent workflow + Dolt sync |
Dolt-backed distributed store |
Task history |
| Gas Town | Beads-backed |
Not documented |
Multi-agent runtime |
Beads ledger |
Refinery merge-queue gates |
| Claude Code agent teams | Shared list with dependencies |
File-locked self-claim |
Lead + teammates, experimental |
One Claude Code session |
TaskCompleted hook can block |
| Backlog.md | Board + dependencies |
Not documented |
Not documented |
Markdown in Git |
Acceptance criteria |
Memory
| Project | Durable memory | Capture and recall | Care and operations | Learning | Provenance |
|---|---|---|---|---|---|
| Brigade | Shared files + cards |
Linted handoffs + bounded recall |
Owner policy + Memory Operations |
Outcome score, promote, rollback |
Work receipts + sources |
| agentmemory | Shared coding-agent memory |
Hooks + MCP + REST |
Decay, audit, governed delete |
Lessons + reflect |
Write-time origin + citations |
| Hindsight | Facts + experiences + models |
Retain + recall |
Reflect + feedback |
Reflective memory learning |
Temporal + causal links |
| Mem0 | User + agent + session |
Extraction + hybrid search |
History + metadata |
Extraction + retrieval |
Timestamps + entities |
| Built-in harness memory | Per tool |
Rules + auto memory |
Varies by harness |
Harness-specific |
Harness-specific |
Tools and configuration
| Project | MCP | Rules and skills | Projection | Source of truth | Audit and rollback |
|---|---|---|---|---|---|
| Brigade | MCP + tools catalog |
Skills + harness adapters |
Dry run first, then write |
Brigade catalog |
Preserve, gate, roll back |
| Rulesync | Supported |
Rules, skills, hooks, subagents |
Per-target generation |
Rulesync project |
Generated outputs |
| Ruler | Supported |
Rules, skills, subagents |
Per-agent files |
.ruler/ directory |
Gitignore automation, no rollback |
| add-mcp | MCP servers |
Not documented |
Maps fields into native files |
Native files + sync |
Warns on dropped fields |
| agentsync | Many agent targets |
Skills, hooks, memory, plugins |
Native/lossy/skipped report |
Canonical config |
Native/lossy/skipped report |
Evidence and operations
| Project | Receipts | Code impact | Agent activity | Cloud state | Replay and learning |
|---|---|---|---|---|---|
| Brigade | Command + exit code + Git state |
Impact queries + blast radius |
Center, fleet board, harness sessions |
Codex, Cursor, Jules task status |
Score + rollback, run diff/resume |
| ActiveGraph | Event trace |
Not documented |
Reactive behaviors |
Not documented |
Replay, fork, and diff |
| Graphiti | Episode provenance |
Not documented |
Not documented |
Not documented |
Temporal fact updates |
| Codex Cloud | Changed files + test results |
Not documented |
Task review |
Hosted task workspaces |
Not documented |
"Not documented" means the capability was not found in that project's official README or docs on the dated pass. It is not proof of absence.
Scope
Brigade coordinates agent work through local records and optional long-running services that the operator starts and can stop. The work ledger is machine-local JSON, and the fleet hub coordinates claims and events without replacing local records. Run budgets apply only when declared. Gates mark checkpoints where the operator wants approval. Agent work can continue within its authorized scope between those checkpoints, leaving receipts and journals for inspection. Full boundaries and service lifecycles: execution model.
Name collisions: this is brigade-cli from escoffier-labs/brigade, not the archived CNCF Kubernetes Brigade, Spinabot Brigade, or the 2017 Python package that became Nornir.
Docs
- First 10 minutes · Overview · Technical guide · Comparison
- Execution model · Work closeout · Outcome scoring
- Memory care · Memory operations · Code intelligence · MCP sync
- Agents guide · Agent-assisted setup · README coverage
- Runbooks · Fleet hub on a Proxmox LXC
- Security · Command inventory · Contributing · Roadmap
License
MIT. See LICENSE.
Project identity: GitHub escoffier-labs/brigade, website brigade.tools, PyPI brigade-cli, npm @escoffier-labs/brigade, command brigade.
1 maintainer
Metadata
1 maintainer
Release files for brigade-cli 0.31.0.dev20261021
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| brigade_cli-0.31.0.dev20261021-py3-none-any.whl | Python 3 | none | any | Details |
Release files / brigade_cli-0.31.0.dev20261021-py3-none-any.whl
| Download URL | brigade_cli-0.31.0.dev20261021-py3-none-any.whl |
|---|---|
| Size | 4.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
22dce74ab5292c5afa97f3402deb47eefcb1d3188df167f744e91365f7cbb2e1
|
|
BLAKE2b-256 checksum How to use checksums |
59086edc9b26da3098a0cca0507dedc9813e6e383a31e8e309f6126ac1453284
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for brigade-cli 0.31.0.dev20261021
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 1 file in this release has been uploaded with provenance metadata.
Attestation for brigade_cli-0.31.0.dev20261021-py3-none-any.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
