Summary
On Windows, the prebuilt squad binary installs and runs, but squad setup has several Windows/Codex compatibility problems:
squad setup auto-detection reports all supported AI tools as missing even when claude, gemini, and codex are available in PATH.squad setup <platform> fails with HOME not set on a normal Windows environment that has USERPROFILE but not HOME.- The generated Codex skill file has invalid YAML frontmatter because the
description value contains an unquoted Usage: segment.
Environment
- OS: Windows
- squad:
0.7.6
- Install method: GitHub Releases,
squad-x86_64-pc-windows-msvc.zip
- AI tools present in PATH:
claude.exegemini.cmdcodex.cmd / codex.exe
Reproduction
1. Auto-detection fails on Windows
Install the Windows release, add the install directory to PATH, then run:
squad setup --list
squad setup
Observed:
Supported platforms:
claude (claude: not found)
gemini (gemini: not found)
codex (codex: not found)
opencode (opencode: not found)
Detecting installed AI tools...
No supported AI tools found in PATH.
Supported: claude, gemini, codex, opencode
However, Windows can find the tools with where.exe, for example:
where.exe codex
where.exe claude
Expected:
squad setup should detect installed tools on Windows.
Likely cause:
The setup detection appears to invoke which <binary>. Windows normally uses where.exe, and which is not available by default.
2. HOME not set on Windows
Run:
Observed:
Error: HOME not set
Caused by:
environment variable not found
Expected:
On Windows, squad should fall back to USERPROFILE or another standard home-directory API instead of requiring HOME.
3. Generated Codex SKILL.md has invalid YAML
After setting HOME and running:
The generated file is:
%USERPROFILE%\.codex\skills\squad\SKILL.md
It starts with:
---
name: squad
description: Join squad multi-agent collaboration. Usage: $squad <role> [custom-id]
squad-version: 0.7.6
---
Codex CLI then reports:
Skipped loading 1 skill(s) due to invalid SKILL.md files.
%USERPROFILE%\.codex\skills\squad\SKILL.md: invalid YAML: mapping values are not allowed in this context at line 2 column 57
Expected:
The description should be quoted, for example:
description: "Join squad multi-agent collaboration. Usage: $squad <role> [custom-id]"
Suggested fixes
- Use a cross-platform executable lookup crate/API, or use
where.exe on Windows and which on Unix.
- Resolve the home directory using a cross-platform home-dir mechanism, falling back to
USERPROFILE on Windows.
- Quote generated YAML frontmatter strings that contain
: or other YAML-special characters.
Thanks for publishing Windows builds. The core binary works; these issues seem specific to the setup/install integration path on Windows.
Summary
On Windows, the prebuilt
squadbinary installs and runs, butsquad setuphas several Windows/Codex compatibility problems:squad setupauto-detection reports all supported AI tools as missing even whenclaude,gemini, andcodexare available inPATH.squad setup <platform>fails withHOME not seton a normal Windows environment that hasUSERPROFILEbut notHOME.descriptionvalue contains an unquotedUsage:segment.Environment
0.7.6squad-x86_64-pc-windows-msvc.zipclaude.exegemini.cmdcodex.cmd/codex.exeReproduction
1. Auto-detection fails on Windows
Install the Windows release, add the install directory to
PATH, then run:squad setup --list squad setupObserved:
However, Windows can find the tools with
where.exe, for example:Expected:
squad setupshould detect installed tools on Windows.Likely cause:
The setup detection appears to invoke
which <binary>. Windows normally useswhere.exe, andwhichis not available by default.2.
HOME not seton WindowsRun:
Observed:
Expected:
On Windows,
squadshould fall back toUSERPROFILEor another standard home-directory API instead of requiringHOME.3. Generated Codex SKILL.md has invalid YAML
After setting
HOMEand running:The generated file is:
It starts with:
Codex CLI then reports:
Expected:
The description should be quoted, for example:
Suggested fixes
where.exeon Windows andwhichon Unix.USERPROFILEon Windows.:or other YAML-special characters.Thanks for publishing Windows builds. The core binary works; these issues seem specific to the setup/install integration path on Windows.