Squad for Claude Code: a coordinator that routes work to a team of specialist subagents, with shared team state in the squad_state MCP server.

Version 2.0.0-preview.4. Squad https://github.com/github/squad.

• The coordinator agent squad:squad.
• The squad_state MCP server, with no .mcp.json approval step and no --mcp-config flag.
• The coordinator's on-demand skills and Squad's template skills (/squad:<skill>).
• Slash commands: /squad:ralph, /squad:cast, /squad:ceremony, /squad:status, /squad:dashboard.
• Squad's advisory governance hooks. They act only when .squad/config.json has "claudeHooks": "advisory".
• squad on the Bash PATH. The launcher runs, in order: SQUAD_CLI, the project's node_modules/@bradygaster/squad-cli, or a squad on PATH. With none of them it fails and says how to install the CLI; set SQUAD_ALLOW_NPX=1 to let it run npx -y @bradygaster/squad-cli@2.0.0-preview.4 instead.

claude plugin marketplace add github/squad
claude plugin install squad@squad --scope project

Then, in the repository:

Install the Squad CLI in your terminal first (the plugin's Bash PATH is available only inside Claude Code):

npm install -g @bradygaster/squad-cli
squad init --client claude --claude-plugin
claude

--claude-plugin records "claudePlugin": true in .squad/config.json. squad init and squad upgrade then write only the per-repository files: member subagents in .claude/agents/, the CLAUDE.md block, and two keys in .claude/settings.json (agent, so a plain claude starts the coordinator, and disabledMcpjsonServers, so the project's .mcp.json copy of squad_state does not prompt or duplicate the plugin's tools). Keep the generated .claude/.squad-plugin-settings.json ownership record with these files: it restores pre-existing settings when switching modes or uninstalling.

Requires Node.js 22.5 or later on PATH.