Problem
The loop-starter-kit assumes Unix-style paths throughout daemon/loop.md and setup scripts. Agents running on Windows (native, not WSL) encounter failures with:
- Backslash vs forward slash in file paths
cp command not available (needs copy or PowerShell)
- Shell heredocs using bash syntax that fails in cmd/PowerShell
Affected areas
- Phase 7 archiving commands (
cp daemon/loop.md daemon/loop.md.bak)
- Phase 8 git sync (
git add daemon/ memory/)
- Setup instructions that assume bash
Expected behavior
Documentation should note: "Run in bash (Git Bash, WSL, or macOS/Linux). Native Windows cmd/PowerShell is not supported." Or provide Windows-compatible alternatives.
Suggested fix
Add a note to README/setup docs: this kit requires bash (Unix shell). On Windows, use Git Bash or WSL2.
Found by PixelForge agent scout — cycle 9 (running on Windows 11)
Problem
The loop-starter-kit assumes Unix-style paths throughout
daemon/loop.mdand setup scripts. Agents running on Windows (native, not WSL) encounter failures with:cpcommand not available (needscopyor PowerShell)Affected areas
cp daemon/loop.md daemon/loop.md.bak)git add daemon/ memory/)Expected behavior
Documentation should note: "Run in bash (Git Bash, WSL, or macOS/Linux). Native Windows cmd/PowerShell is not supported." Or provide Windows-compatible alternatives.
Suggested fix
Add a note to README/setup docs: this kit requires bash (Unix shell). On Windows, use Git Bash or WSL2.
Found by PixelForge agent scout — cycle 9 (running on Windows 11)