How do I confirm it is fixed?

hive mind spawn claude no longer reports a missing claude command; the related child process starts normally a claude session appears in the logs .

What about other environments?

WSL / Linux: the local swarm path was measured working 2026 08 30 ; Windows: PATH semantics and shim recognition are a common pitfall 3071 ; Source material: ruvnet/ruflo issue 3071 closed, 2026 08 20 , anonymous retrieval summary; the Windows path was not reproduced here stated honestly .

Problem: `hive-mind spawn --claude` cannot find the claude CLI on Windows (PATH detection failure) —

Q: What problem will I run into?

On Windows you run hive mind spawn claude and ruflo says the claude command cannot be found — yet claude runs fine in your own terminal or you just installed it . This is a classic cross tool PATH detection failure : the other tool does not understand Windows PATH semantics.

Q: How do I fix it quickly?

Two Windows checks same mechanism on Unix : 1 claude version verify the CLI itself works; 2 where claude see whether its location is on PATH; if not, add that directory to PATH or the system PATH and reopen the terminal; Still unrecognized: call it by full path, and check whether the npm global bin directory home of the claude.cmd shim is on PATH.

Quick fix

Two Windows checks (same mechanism on Unix):
1) claude --version        verify the CLI itself works;
2) where claude            see whether its location is on PATH; if not, add that directory to PATH (or the system PATH) and reopen the terminal;
Still unrecognized: call it by full path, and check whether the npm global bin directory (home of the claude.cmd shim) is on PATH.

What you will run into

On Windows you run hive-mind spawn --claude and ruflo says the claude command cannot be found — yet claude runs fine in your own terminal (or you just installed it). This is a classic cross-tool PATH detection failure: the other tool does not understand Windows PATH semantics.

Why this happens

Conclusion first: PATH detection failure (issue #3071, closed 2026-08-20) — Windows PATH semantics and install locations differ sharply from Unix, and the detector did not recognize the claude CLI.

Chain: ruflo spawn -> probe for the claude executable -> Windows PATH lookup (.cmd/.exe shims, npm global bin directories) -> miss -> "command not found". The break: the install location is not on PATH, or the probe does not understand shims.

Side-by-side measurement: the local swarm path works in this environment (WSL Linux;）; the Windows PATH path was not reproduced (stated honestly).

Conclusion: for cross-tool integration failures, start with two manual checks — does claude --version run, and where is it (where claude)? If it runs, the problem is in the detection layer: add the directory to PATH or use the full path.

Step by step

1. Verify the claude CLI manually — Required

claude --version + where claude: if the command itself works, the problem is the detection layer, not the installation.

2. Add the directory to PATH — Required

In the system environment variables, add the claude directory (including the npm bin directory that holds the claude.cmd shim) to PATH, reopen the terminal, and retry.

3. Full path as a fallback — By scenario

If the detecting tool supports a custom path, point it at the full claude executable path.

4. Follow the issue if it persists — Diagnostic

If PATH is verified correct but detection still fails, follow the resolution of ruvnet/ruflo #3071 (closed) or open a new issue.

How to confirm it works

hive-mind spawn --claude no longer reports a missing claude command;
the related child process starts normally (a claude session appears in the logs).

Other environments

WSL / Linux: the local swarm path was measured working (2026-08-30);
Windows: PATH semantics and shim recognition are a common pitfall (#3071);
Source material: ruvnet/ruflo issue #3071 (closed, 2026-08-20), anonymous retrieval summary; the Windows path was not reproduced here (stated honestly).

Symptom

On Windows, running spawn --claude reports that the claude command cannot be found.

Cause

PATH detection failure (issue #3071, closed 2026-08-20): Windows PATH semantics / install locations differ, and the claude CLI was not recognized.

Solution

Add the directory containing the claude executable to PATH, then call it (or use the full path).
Confirm the claude CLI is installed (claude --version).

Verification Evidence

Material: issue #3071 (closed, 2026-08-20), anonymous retrieval summary; this environment is WSL Linux, so the Windows PATH path was not reproduced (stated honestly).

Applicable tools (1)

This problem is linked from the tool pages below — reachable from either side.

ruflo

Source & evidence

Recorded 2026-09-19Verified ✓ VerifiedApplies to 1 tool(s)

Entries contain locally measured or reviewable-source solutions; unmeasured items are explicitly labeled.

← Multi-Agent Orchestration domain ｜ Problem Catalog Experience ｜ Facing another issue? Go to the Helpdesk