Назад към всички

hive-mind

// Byzantine fault-tolerant consensus and distributed coordination. Queen-led hierarchical swarm management with multiple consensus strategies. Use when: distributed coordination, fault-tolerant operations, multi-agent consensus, collective decision making. Skip when: single-agent tasks, simple operati

$ git log --oneline --stat
stars:18,689
forks:3.6k
updated:February 28, 2026
SKILL.mdreadonly
SKILL.md Frontmatter
namehive-mind
descriptionByzantine fault-tolerant consensus and distributed coordination. Queen-led hierarchical swarm management with multiple consensus strategies. Use when: distributed coordination, fault-tolerant operations, multi-agent consensus, collective decision making. Skip when: single-agent tasks, simple operations, local-only work.

Hive-Mind Skill

Purpose

Byzantine fault-tolerant consensus and distributed swarm coordination.

When to Trigger

  • Multi-agent distributed tasks
  • Fault-tolerant operations needed
  • Collective decision making
  • Complex coordination patterns

Topologies

TopologyDescriptionUse Case
hierarchicalQueen controls workersDefault, anti-drift
meshFully connected peersResearch, exploration
hierarchical-meshHybridRecommended for complex
adaptiveDynamic based on loadAuto-scaling

Consensus Strategies

StrategyToleranceUse Case
byzantinef < n/3 faultyUntrusted environment
raftf < n/2 faultyLeader-based, consistent
gossipEventualLarge scale, availability
crdtConflict-freeConcurrent updates
quorumConfigurableTunable consistency

Commands

Initialize Hive-Mind

npx claude-flow hive-mind init --topology hierarchical-mesh --consensus raft

Spawn Queen

npx claude-flow hive-mind spawn --role queen --name coordinator

Check Consensus Status

npx claude-flow hive-mind consensus --status

View Sessions

npx claude-flow hive-mind sessions --active

Best Practices

  1. Use hierarchical for coding tasks (anti-drift)
  2. Use raft consensus for consistency
  3. Keep agent count under 8 for coordination
  4. Run frequent checkpoints