Back to Details

hive-mind

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Hive-Mind Skill

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
  • 多Agent分布式任务
  • 需要容错操作
  • 集体决策
  • 复杂协调模式

Topologies

拓扑结构

TopologyDescriptionUse Case
hierarchical
Queen controls workersDefault, anti-drift
mesh
Fully connected peersResearch, exploration
hierarchical-mesh
HybridRecommended for complex
adaptive
Dynamic based on loadAuto-scaling
拓扑结构描述适用场景
hierarchical
女王节点控制工作节点默认选项，防止偏移
mesh
全连接对等节点研究、探索场景
hierarchical-mesh
混合模式推荐用于复杂场景
adaptive
根据负载动态调整自动扩容

Consensus Strategies

共识策略

StrategyToleranceUse Case
byzantine
f < n/3 faultyUntrusted environment
raft
f < n/2 faultyLeader-based, consistent
gossip
EventualLarge scale, availability
crdt
Conflict-freeConcurrent updates
quorum
ConfigurableTunable consistency
策略容错能力适用场景
byzantine
可容忍少于n/3的故障节点不可信环境
raft
可容忍少于n/2的故障节点基于领导者模式，一致性优先
gossip
最终一致性大规模场景，可用性优先
crdt
无冲突并发更新场景
quorum
可配置可调节一致性

Commands

命令

Initialize Hive-Mind

初始化Hive-Mind

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

Spawn Queen

生成女王节点

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

Check Consensus Status

检查共识状态

bash
npx claude-flow hive-mind consensus --status
bash
npx claude-flow hive-mind consensus --status

View Sessions

查看会话

bash
npx claude-flow hive-mind sessions --active
bash
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
  1. 编码任务使用hierarchical模式（防止偏移）
  2. 一致性需求场景使用raft共识
  3. 协调的Agent数量控制在8个以内
  4. 频繁运行检查点