Search Brigade

Search Brigade pages and docs.

How Brigade compares

Brigade overlaps several categories. Where another project is stronger, the table says so. Every cell was checked 2026-09-28: Brigade against the published v0.27.0 release, other projects against their current official docs, linked under Sources.

Supported Partial Not documented
Supported
The checked official sources document the capability in the scope the cell names.
Partial
The sources document a subset, an indirect route, or something the operator or application has to build.
Not documented
Not found in the checked sources. This is not proof the project lacks it.

Work and orchestration

ProjectReady workClaim safetyParallel and run controlTask-store boundaryVerification
Brigade Supported Stable ready set Supported Fail-closed local CAS + optional hub claims Partial Per-repo and campaign waves, declared wall-clock and dispatch ceilings, named retry/reroute Partial Local JSON ledger. Optional hub for events/claims, not a task DB Supported Command + exit code + Git receipts
Beads Supported Dependency-unblocked tasks Supported Atomic claim Partial Multi-agent workflows + Dolt sync Supported Dolt-backed distributed store Partial Task history + audit trail
Gas Town Supported Beads-backed ready work Supported Local dispatch + assignee locks Supported Scheduler caps, pause/resume + agents Supported Beads-backed task store Supported Refinery verification + merge gates
nWave Partial Guided wave entry Not documented Partial 7 waves with review + TDD gates Partial Git-tracked artifacts Supported TDD hooks + CI phase validation
ActiveGraph Supported Reactive graph triggers Partial Optimistic patches, app-defined claims Supported Bounded runs + cooperative drains Supported Append-only event log Partial Event trace + replay

Memory

ProjectDurable memoryCapture and recallCare and operationsLearningProvenance
Brigade Supported Shared files + cards Supported Linted handoffs + bounded recall Supported Owner policy, care review queue, vault project/search/propose Partial Manifest-scored outcomes + promote + rollback Supported Work receipts + sources
Mem0 Supported User + agent + session stores Supported Fact extraction + hybrid search Supported Edit, delete, history + export Partial Extraction + deduplication Partial IDs, timestamps + change history
Letta Supported Agent state + shared blocks Supported Agent-edited blocks + archival search Supported Block controls + archive CRUD Partial Agent-managed memory updates Partial Source IDs + record metadata
agentmemory Supported Shared coding-agent memory Supported Hooks + hybrid and graph recall Supported Versioning, retention + rollback Supported Reflection, lessons + consolidation Supported Origin channels + source citations
Hindsight Supported Facts, experiences + mental models Supported Retain, recall + reflect Supported Document history + model refresh Supported Reflective memory learning Supported Document/chunk citations + metadata
Built-in harness memory Supported Tool-specific files + stores Partial Rules + opt-in or automatic recall Partial Per-tool inspection + controls Partial Saved corrections + consolidation Partial Files + prior-chat evidence, varies by tool
OpenClaw Supported Plain files + index Supported Hybrid search + optional session recall Supported Consolidation, review + forgetting Supported Dreaming + gated promotion Supported Origin metadata + change history

Tools and configuration

ProjectMCPReviewed rules and skillsProjection behaviorSource of truthAudit and rollback
Brigade Supported MCP + tools catalog Supported Skills + adapters Supported Dry-run-first, then apply Supported Brigade catalog Supported Preserve + gate + rollback
add-mcp Supported MCP servers + native client configs Not documented Supported Native field mapping + loss warnings Partial Registry + native files Partial List/remove/sync + dropped-field warnings
Rulesync Supported MCP per target Supported Rules, skills, hooks + commands Supported Per-target generation Supported .rulesync source tree Partial Generated-file cleanup
aiconfigsync Not documented Partial Rules only Supported Generated rule files Supported .claude/rules source Partial Dry-run + generated headers
chezmoi Partial As files Partial As files Supported Templates, dry-run + apply Supported Git-backed source dir Supported Git history, diff + apply restore
agentsync Supported MCP across agent targets Supported Rules, skills, hooks + commands Supported Native/lossy/skipped report Supported Canonical .agentsync tree Supported Git checkpoints + revert

Evidence and operations

ProjectReceiptsCode impactAgent activityCloud stateLearning / replay
Brigade Supported Command + Git + optional impact + run lineage Supported Code impact, code-graph views, blast radius Supported Center activity, fleet board, best-effort external harness sessions Supported Cloud launch, best-effort status, approved Grok Bot scout feed Partial Manifest-scored promote + rollback, run child/diff/resume
ActiveGraph Partial Event trace + export Not documented Partial Behavior + tool events Not documented Supported Replay, fork + diff
CocoIndex Partial Data lineage Partial Semantic + structural search via separate CocoIndex Code Not documented Not documented Partial Incremental recompute + cached transforms
Graphiti Partial Episode provenance + validity windows Not documented Partial Optional OpenTelemetry operation traces Not documented Partial Temporal history + fact invalidation
Hindsight Partial Recall traces + memory history Not documented Partial Memory lifecycle hooks + session tags Not documented Supported Reflective memory learning
Neo4j Agent Memory Partial App-recorded reasoning + audit edges Not documented Partial Recorded tool calls + reasoning steps Not documented Partial Similar-task retrieval + memory evals

Scope

Every neighbor cell was re-checked on 2026-09-28 against the current official README, docs, or package page linked under Sources. Optional features may need configuration, and a packaged release can lag or differ from current docs. Brigade cells were re-checked on 2026-09-28 against the published v0.27.0 release. Unreleased 0.28 beta changes on Brigade main are not counted.

Cloud state means tracking work that a cloud coding agent runs: launch, provider IDs, and status. Cloud-hosted memory or cloud embeddings do not count.

The evidence table’s Learning / replay column counts either reflective memory learning or execution replay. The memory table’s Learning column describes memory learning.

Care and operations counts documented memory edit, delete, history, and access controls. It does not require Brigade-style owner policy.

Provenance built only from IDs, timestamps, and change history is Partial. Explicit citations back to source observations are Supported.

Receipts, event traces, memory history, and data lineage answer different questions. A Partial receipts cell means a different kind of record, not a weaker command receipt.

Brigade is a local file-first control plane for coding agents. Nothing runs until a command or an operator-owned scheduler starts it. Optional Center, Run View, and fleet hub serve commands stay in the foreground until you stop them. The schedule belongs to the operator. On request, brigade care install registers target-scoped systemd user timers or launchd agents that the operator can inspect and uninstall. Brigade runs no daemon or supervisor of its own.

The work ledger is machine-local JSON and is not a distributed task database. An optional fleet hub aggregates run events and arbitrates repo claims. The fleet board can show external harness sessions. Local journals stay authoritative. An approved Grok Bot scout feed enqueues labeled GitHub issues only after --apply.

Ordinary runs have no hard run-budget. A run started with a declared budget gets hard wall-clock and worker-dispatch ceilings, and Brigade refuses new dispatch past them. Cancelling workers already in flight is best-effort. Model, tool, token, and cost dimensions stay observed unless an adapter owns an enforcement boundary.

Campaigns aggregate ready work across repos and compose parallel-safe waves at query time from each member's per-repo partition. Center web views, the hub Command Deck, and the fleet board are read-only. Center CLI commands can write local reports, action records, and work imports. The hub roster page lets an admin save seat and routing settings.

brigade run cloud launch can start Cursor Cloud or Jules work from a bounded prompt file. The provider runs that work. Brigade records the provider IDs and reports status as best-effort observations. External activity observations are best-effort too.

Memory care scans cards and queues review work. It does not rewrite card text. Only memory care backfill --apply adds derived frontmatter, with a receipt. Safe targeted handoffs may auto-file under owner policy. Ambiguous or risky notes wait for review.

Outcome learning scores only receipts from verify manifests tracked under verify/manifests/. Ad-hoc --command and --argv-json receipts are audit-only evidence for a human reader. Learning is scored verification, not reflective memory learning.

Brigade is not a hosted memory service, automatic release bot, or full autonomous fleet runtime. It does not push to GitHub, publish packages, or send chat messages unless the operator uses an explicit send action.

Brigade sources, pinned to the v0.27.0 commit: README scope, Outcome scoring, Run budgets and cloud launch, Operator Center, Fleet hub, Scheduled care, Memory care.

Sources

Official sources behind each neighbor row, checked 2026-09-28.