[macOS] hive-mind spawn hangs: printed Swarm ID never shows up in hive-mind status, workers stay idle, tasks remain 0
#654
Unanswered
mgredenberg
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
I cannot get claude-flow running properly on my system.
Following the README instructions, spawning a new Hive Mind reports that the swarm is initialized and workers are starting, but then everything stalls. The Swarm ID printed by
spawnnever appears inhive-mind status. Instead,statusshows a different swarm with0tasks and all workersidle. Waiting >3,000 seconds shows no progress.There also appears to be an ID mismatch/normalization issue: the
spawnoutput uses an ID with underscores, whilestatusshows a different ID with hyphens and different numeric segments. An MCPmemory_usagestore event writes to yet another swarm namespace, suggesting the components aren’t referencing the same swarm.Steps to Reproduce
In a clean project directory, initialize:
Spawn a hive mind (per docs):
npx claude-flow@alpha hive-mind spawn "gameplay" --namespace gameplay --claudeObserve the spawn output and then check status:
Expected Behavior
spawnappears inhive-mind status.idletoin progress.Actual Behavior
spawnprints an initialized swarm and “deploying” message, then stalls indefinitely. Example:MCP events show mixed IDs/namespaces:
hive-mind statusshows another swarm entirely, with no tasks and all workersidle:After >3,000 seconds, nothing progresses.
Observations / Hypothesis
memory_usagestoring under a different swarm namespace further indicates cross-wiring between IDs.Workarounds Tried
init --force.spawnand pollingstatusfor >3,000 seconds.No effective workaround found.
Environment
npx claude-flow@alphaBeta Was this translation helpful? Give feedback.
All reactions