Problem
scripts/install.sh is bash-only and requires uv, pipx, or Python >= 3.12 to already exist (scripts/install.sh step 1/4 never bootstraps uv). A Windows machine with none of them cannot install Ouroboros without first setting up WSL 2 or a Python toolchain by hand. The README only shows the curl | bash one-liner.
The Claude Code plugin path does not actually need a system Python: .claude-plugin/.mcp.json launches the MCP server through uvx --python '>=3.12', skills fall back to uv run, and hooks fail open. The real prerequisites on native Windows are Git and uv.
Proposed
A scripts/install.ps1 runnable as irm .../install.ps1 | iex on PowerShell 5.1+ that installs Git and uv through winget when missing, runs uv tool install ouroboros-ai with the same pins as install.sh, and wires setup + the Claude Code plugin. README/getting-started should show both one-liners.
Related: #2050 (single-file exe distribution — a different, longer-term path).
Problem
scripts/install.shis bash-only and requires uv, pipx, or Python >= 3.12 to already exist (scripts/install.shstep 1/4 never bootstraps uv). A Windows machine with none of them cannot install Ouroboros without first setting up WSL 2 or a Python toolchain by hand. The README only shows thecurl | bashone-liner.The Claude Code plugin path does not actually need a system Python:
.claude-plugin/.mcp.jsonlaunches the MCP server throughuvx --python '>=3.12', skills fall back touv run, and hooks fail open. The real prerequisites on native Windows are Git and uv.Proposed
A
scripts/install.ps1runnable asirm .../install.ps1 | iexon PowerShell 5.1+ that installs Git and uv through winget when missing, runsuv tool install ouroboros-aiwith the same pins asinstall.sh, and wires setup + the Claude Code plugin. README/getting-started should show both one-liners.Related: #2050 (single-file exe distribution — a different, longer-term path).