Metadata-Version: 2.4
Name: brigade-cli
Version: 0.31.0.dev20261102
Summary: Run coding agents anywhere and keep one record of the work, with MCP servers, tools, skills, and memory in sync across your harnesses.
Author-email: Solomon Neas <me@solomonneas.dev>
License: MIT
Project-URL: Homepage, https://brigadestack.com
Project-URL: Documentation, https://brigade.tools/docs
Project-URL: Compare, https://brigade.tools/compare/sync-mcp-servers-across-coding-agents
Project-URL: Handoffs, https://brigade.tools/compare/memory-handoffs-across-coding-agents
Project-URL: CodeGraph, https://brigade.tools/compare/local-code-graph-for-ai-coding-agents
Project-URL: Evidence, https://brigade.tools/compare/local-evidence-ledger-for-agent-work
Project-URL: Skills, https://brigade.tools/compare/portable-skills-across-coding-agents
Project-URL: LLMs, https://brigade.tools/llms.txt
Project-URL: Repository, https://github.com/escoffier-labs/brigade
Project-URL: Cookbook, https://escoffierlabs.dev/cookbook/
Project-URL: CookbookSource, https://github.com/escoffier-labs/solos-cookbook
Project-URL: OpenClaw, https://github.com/solomonneas/openclaw
Project-URL: ContentGuard, https://github.com/escoffier-labs/content-guard
Project-URL: AgentPantry, https://github.com/escoffier-labs/agentpantry
Project-URL: EvidenceMemory, https://brigade.tools/evidence-memory
Project-URL: CodeIntelligence, https://brigade.tools/code-intelligence
Project-URL: Issues, https://github.com/escoffier-labs/brigade/issues
Keywords: agents,ai-agents,agent-memory,agent-handoffs,ai-memory,mcp,mcp-config,mcp-sync,model-context-protocol,openclaw,claude-code,codex,opencode,grok,hermes,memory,bootstrap,brigade,brigade-cli,operator,local-first,guardrails,agents-md,code-graph,evidence-ledger,mcp-server,agent-skills
Classifier: Development Status :: 3 - Alpha
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Operating System :: Microsoft :: Windows
Classifier: Operating System :: MacOS
Classifier: Operating System :: POSIX :: Linux
Requires-Python: >=3.10
Description-Content-Type: text/markdown
License-File: LICENSE
Provides-Extra: mesh
Requires-Dist: cryptography<52,>=50.0.2; extra == "mesh"
Provides-Extra: dev
Requires-Dist: cryptography<52,>=50.0.2; extra == "dev"
Requires-Dist: pytest<9.2,>=9.1.1; extra == "dev"
Requires-Dist: pytest-cov>=7.1.0; extra == "dev"
Requires-Dist: pytest-xdist>=3.8.0; extra == "dev"
Requires-Dist: ruff>=0.17.1; extra == "dev"
Requires-Dist: mypy>=2.4.0; extra == "dev"
Provides-Extra: grokbot
Requires-Dist: mcp<3,>=2.3.0; extra == "grokbot"
Requires-Dist: pyjwt[crypto]>=2.15.1; extra == "grokbot"
Provides-Extra: research
Requires-Dist: playwright>=1.64.0; extra == "research"
Dynamic: license-file

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

<p align="center">
  <strong>Coordinate your agents. Keep the tools you use.</strong>
</p>

Brigade Stack is an open-source coordination layer for AI coding agents. It sits beside Codex, Claude Code, Cursor, OpenCode, T3 Code, and the rest, and gives them shared tasks, shared memory, and verification records any agent can check.

<p align="center">
  <a href="https://brigade.tools">Website</a> ·
  <a href="https://brigade.tools/docs">Docs</a> ·
  <a href="QUICKSTART.md">Quickstart</a> ·
  <a href="docs/comparison.md">Compare</a> ·
  <a href="CHANGELOG.md">Changelog</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>

**Stable:** v0.30.0 on PyPI and npm. **Beta:** main is the 0.31 preview line. [Channels](docs/update-channels.md)

## Why Brigade Stack

You run several agents at once. Sol in Codex takes one task, Opus manages another, and Argon takes a third here and there, whether they share one window in a multi-harness tool like T3 Code or each run in its own app. Your Grok Bot runs the rest of your life, and your Dots spin up work of their own. Every agent starts from its own conversation. None of them knows who owns which task, what the others already tried, or whether a fix was actually checked.

Brigade Stack holds that state outside any one tool. Agents read the same brief, claim the same tasks, and leave handoffs and evidence the next agent can inspect.

- **Keep your tools.** Works alongside the agents you already use. Start with one tool in one repository and add more when you need them.
- **Work agents can pick up.** Tasks, dependencies, claims, and handoffs make the next action discoverable without replaying a conversation.
- **Checkable results.** Verification records keep the command, exit code, logs, and Git state, so another agent can confirm "tests pass" for itself.
- **You set the limits.** Model access, scopes, budgets, and approval gates apply to Brigade-managed work, and you can inspect or stop it.

## How it works

1. **Start with context.** Agents begin from a work brief: relevant memory, open tasks, and existing evidence.
2. **Claim the work.** Ownership is explicit, and conflicting or dependent work is visible.
3. **Run within your rules.** Managed execution uses your configured models, scopes, budgets, and approvals.
4. **Verify the result.** Checks run through Brigade and leave a record another agent can inspect.
5. **Hand off.** The result, remaining blockers, and evidence stay where the next agent will find them.

A local setup needs no server. Fleet Hub adds shared ownership, presence, messaging, and model policy across machines when you want it. See the [execution model](docs/execution-model.md).

## Quick start

Install the stable bridge with npm (Node.js `^22.15.0 || >=23.11.0`):

```bash
npm install --global brigadestack@0.30.0
brigadestack --version
```

In a Git repository you control, preview the setup, apply it, and read the brief:

```bash
brigadestack operator quickstart --target . --harnesses codex --dry-run
brigadestack operator quickstart --target . --harnesses codex
brigadestack work brief --target .
```

Replace `codex` with the harnesses you use, such as `codex,claude`. Record a first check:

```bash
brigadestack work verify run --target . --command "git diff --check" --capture brigade-work
```

This checks whitespace in your unstaged diff and records the command, exit code, and logs. Use your project's test command for subsequent checks. The [first 10 minutes](docs/first-10-minutes.md) walks through health checks and receipt inspection.

The npm bridge exposes `brigadestack` and downloads a managed Python on first launch. Git is required for this walkthrough. For Python installs, platform limits, optional engine setup, and existing `brigade` installs, see [Quickstart](QUICKSTART.md#1-install). Existing commands, Python imports, and `.brigade/` data remain compatible.

Generated agent instructions and CLI suggestions still use `brigade`. On a bridge-only install, run those commands as `brigadestack` and tell your agents to do the same. Existing `brigade` installs need no change.

## Works with

| Tool | Connection |
| --- | --- |
| **Codex, Claude Code, Cursor, OpenCode** | Workspace instructions, handoff inboxes, and tool and skill configuration. Hooks vary by tool. |
| **T3 Code** | Remote execution and session visibility. Full child-task governance is in progress. |
| **Grok Bot** | Role-scoped connector packs for bounded jobs. |
| **OpenClaw, Hermes** | Memory-owner workflows, writer handoffs, and memory care. |
| **Dot** | Memory, skills, Hub messaging, and authorized T3 fleet dispatch. |
| **Duet** (0.31 beta) | Memory, skills, Hub messaging, and read-only fleet views. |

Hosted connectors need explicit setup. See the [technical guide](docs/technical-guide.md), [Dot guide](docs/grokbot-dot.md), and [Duet guide](docs/duet-connector.md).

## MCP servers

A memory server with bounded recall, work briefs, and handoff drafting, plus a read-only skills server:

```bash
brigadestack memory serve-mcp --stdio
brigadestack skills serve-mcp --stdio
```

`write_handoff` drafts a handoff and never edits a canonical card. [Transport details](docs/technical-guide.md#streamable-http-for-the-mcp-servers)

<!-- MCP Registry ownership markers; keep each on its own line. -->
<!-- mcp-name: io.github.escoffier-labs/brigade-memory -->
<!-- mcp-name: io.github.escoffier-labs/brigade-skills -->

## In the 0.31 beta

- **Parallel workers.** Dispatch ready tasks into separate worktrees, supervise them, and keep results for review.
- **Memory reflection.** Evidence-backed consolidation proposals for review. Nothing is rewritten automatically.
- **Run patrol.** Detects local lane states and offers explicit repair actions.
- **In progress:** [fleet coordination](https://github.com/escoffier-labs/brigade/issues/1121), [governed T3 delegation](https://github.com/escoffier-labs/brigade/issues/2046), [cross-repository campaigns](https://github.com/escoffier-labs/brigade/issues/1128), and the [agent mesh](docs/phase-agent-mesh.md).

## Reference

[Commands](docs/command-inventory.md) · [Execution model](docs/execution-model.md) · [Comparisons](docs/comparison.md) · [Contributing](CONTRIBUTING.md) · [Issues](https://github.com/escoffier-labs/brigade/issues) · [MIT license](LICENSE)

The Python CLI may send a passive version request. [Telemetry](docs/telemetry.md) lists its fields, retention, and opt-outs.

<details>
<summary>About the downloads badge</summary>

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](https://raw.githubusercontent.com/escoffier-labs/brigade/download-metrics/downloads.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.

</details>

Brigade Stack by Escoffier Labs. Project identity: GitHub [`escoffier-labs/brigade`](https://github.com/escoffier-labs/brigade), website [brigade.tools](https://brigade.tools), PyPI [`brigadestack`](https://pypi.org/project/brigadestack/), npm [`brigadestack`](https://www.npmjs.com/package/brigadestack), command `brigadestack`. The `brigade-cli` and `@escoffier-labs/brigade` packages and `brigade` command remain supported.
