Search BrigadeStack

Search BrigadeStack pages and docs.

BrigadeStack
Menu

Comparisons

Which Brigade? BrigadeStack vs Spinabot and Kubernetes

Searching "Brigade" or "BrigadeStack" turns up Spinabot's agent crew, a Kubernetes tool, and an old Python package. Here is which Brigade this is.

Updated November 15, 2026

Short answer: this is BrigadeStack, a local coordination layer for AI coding agents from Escoffier Labs, with source at github.com/escoffier-labs/brigade. It tracks what is ready, who claimed it, and what ran across Claude Code, Codex, cloud agents, and your machines, and keeps their MCP servers, skills, and memory in sync. You install it with pipx install brigadestack or npm install -g brigadestack and run it as brigadestack. It started as brigade-cli, and that package and its brigade command still work. It is not the Kubernetes Brigade, not the Spinabot agent crew, and not the old Python package that became Nornir. Same word, different tools.

Why the name BrigadeStack

Other projects already use the bare name Brigade, so the public name is BrigadeStack, written as one word. The one-word name narrows the overlap in search results and package registries. It does not end it: the Kubernetes and Spinabot projects still use the bare name, and the older package names still say Brigade. The rename adds names and leaves existing ones in place:

  • brigadestack on PyPI and npm installs the same stable CLI as brigade-cli and @escoffier-labs/brigade, pinned to the matching version.
  • The brigade command, .brigade/ workspace files, BRIGADE_* environment variables, and Python imports keep their names.
  • Help output still names the program brigade, and brigadestack --version prints brigade followed by the version.

The Brigades you might have found

NameWhat it isHow to tell
BrigadeStack (this one, Escoffier Labs)coordination layer for AI coding agents: ready work, safe claims, verification receipts, memory handoffs, and MCP, skill, and tool sync across Claude Code, Codex, Cursor, OpenCode, and T3 Codepipx install brigadestack (or the older brigade-cli), site brigadestack.com (formerly brigade.tools), GitHub escoffier-labs/brigade, local files, no required daemon
Brigade (Spinabot)a self-hosted personal-intelligence crew of agents on an org chart, sharing “Tideline” long-term memoryGitHub spinabot/brigade, site brigade.spinabot.com, an always-on gateway on port 7777 (brigade gateway, brigade tui, brigade connect)
Brigade (CNCF / Microsoft)event-driven scripting for Kubernetessite brigade.sh, archived in 2022, about Kubernetes pipelines
brigade (2017 PyPI)an old network-automation packagerenamed to Nornir years ago

Features that belong to Spinabot’s Brigade, not BrigadeStack

Search summaries sometimes merge the two projects. These belong to Spinabot’s Brigade, and BrigadeStack does not have them:

  • Tideline long-term memory. BrigadeStack memory is handoff files filed into markdown cards, plus an evidence ledger.
  • A headless gateway on port 7777 and the brigade gateway, brigade tui, and brigade connect commands. BrigadeStack runs no required daemon.
  • An agent “crew” with personas on an org chart. BrigadeStack coordinates the coding agents you already use.

How to be sure you have the right one

  • The packages are brigadestack and brigade-cli on PyPI, and brigadestack and @escoffier-labs/brigade on npm. None of them is the brigade PyPI package.
  • The commands are brigadestack and brigade, and --version on either reports the Brigade version.
  • The home is brigadestack.com and github.com/escoffier-labs/brigade.
  • It is about coding agents (Claude Code, Codex, Cursor, OpenCode, T3 Code, Hermes, OpenClaw), not Kubernetes and not a personal assistant crew.

If you came here looking for the Kubernetes Brigade, you want brigade.sh, which is now archived. If you wanted the Spinabot agent crew, that is github.com/spinabot/brigade. If you want the coordination layer for your coding agents, you are in the right place.

What BrigadeStack does and the quickstart.