Search Brigade

Search Brigade pages and docs.

by Escoffier Labs

Brigade keeps coding-agent work trackable across tools, repos, and sessions: tasks, receipts, shared memory, and synced tools.

What it does

Ready work and claim safety

Brigade lists unblocked tasks and uses fail-closed atomic claims so two agents cannot take the same item.

Run limits and registered cloud work

Current betaDeclared runs can enforce wall-clock and worker-dispatch ceilings and record named retry or reroute decisions. An optional fleet hub can report runs, repo claims, and external harness sessions. Registered cloud work is reconciled against provider and GitHub state.

Verification receipts

A check run through Brigade records the command, real exit code, Git state, and optional code impact.

Memory handoffs and recall

Handoffs are linted and routed by the memory owner. Ambiguous or risky notes wait for review, and recall returns a bounded relevant set. Current beta adds vault project, search, and propose.

Explicit harness projection

Brigade previews MCP, tool, and skill changes before writing them into each harness. Applying a projection is always explicit.

How Brigade fits

Most adjacent projects specialize in one layer. Brigade connects those layers around trackable coding-agent work.

LayerBrigadeAdjacent projects
Work Ready work, claims, waves, fleet hub, receipts Beads, Gas Town, nWave
Memory Handoffs, care, vault, bounded recall, provenance Hindsight, Mem0, Letta, agentmemory
Tools Dry-run-first MCP, tool, and skill projection Rulesync, add-mcp, chezmoi
Evidence Receipts, blast radius, fleet board, cloud state ActiveGraph, CocoIndex, Graphiti
See the full comparison.

Scope

Install Brigade

Start with the install guide, then let your coding agent wire the harnesses you use.