mesh-coordinator — Claude Code subagent: what it does, how to install
mesh-coordinator — a coordinator subagent that links agents into a peer-to-peer mesh: decisions go through voting, peers find each other, and the network keeps going when a node drops.
no license ★ 850 updated 2026-10-26
.claude/agents/mesh-coordinator.mdWhat mesh-coordinator does
Every agent here is a peer. It answers requests and sends them, with no node sitting above the rest. Two hooks bracket the work. Before the task, the coordinator raises a mesh topology capped at 12 agents on the distributed strategy, broadcasts a network-start message and proposes gossip with a 0.67 consensus threshold. When the task ends, it writes metrics into the mesh namespace and tells peers the network is shutting down.
Three ways of spreading work are laid out: taking queued tasks from busy neighbors, a DHT that keeps three copies of each task, and an auction where bids are scored on skill match, current load, past results and free resources. Resilience rests on gossip rounds every 2–5 seconds fanning out to 3–5 peers, tolerance for up to 33% failed nodes, and the phases of pBFT. A joining node bootstraps from seed nodes, then receives the peer list.
The hooks call mcp__claude-flow__ tools such as swarm_init, daa_communication, daa_consensus, memory_usage and performance_report. Without the claude-flow MCP server connected, none of them fire and the file stays a plain instruction sheet.
What it helps with
- split one job across several agents with no central controller
- keep the swarm alive after a node fails and move its work
- reach a decision when part of the agents disagrees
- pass queued work to a peer that has spare capacity
- dump network state to memory and pull a report afterwards
Example prompts for the agent
- Spin up a mesh of 12 agents and split the refactor queue across them.
- Run a consensus round on the migration plan with a 0.67 threshold.
- Find the dead nodes in the mesh and move their tasks to live peers.
How to install mesh-coordinator
Manually: put the files in place
.claude/agents/mesh-coordinator.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/mesh-coordinator.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/mesh-coordinator.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about mesh-coordinator
How do I install mesh-coordinator in Claude Code?
Copy the agent file to .claude/agents/mesh-coordinator.md inside your project.
What does mesh-coordinator do?
It treats agents as equal nodes of one network: builds the mesh topology, hands out tasks and settles decisions by vote. Gossip and quorum keep the network running when a node fails.
Does it work without claude-flow?
No. Its hooks invoke mcp__claude-flow__ tools, so the claude-flow MCP server has to be connected.