How to Install OpenClaw Skills on Windows When Homebrew Is Not Available

Mar 17, 2026

1. The Problem

I just installed OpenClaw on my Windows machine and tried to install the recommended skills. Every single one failed with this error:

pnpm.cmd is not recognized as an internal or external command,
operable program or batch file.
Install Failed

After digging into the logs, I discovered the real issue: OpenClaw defaults to using Homebrew (brew) for skill installation, but Homebrew is a Mac-only package manager. Windows users are left stranded.

2. Why This Happens

OpenClaw assumes a Unix-based system for skill installation. The architecture looks like this:

┌─────────────────────────────────────────────────┐
│                 OpenClaw Core                    │
├─────────────────────────────────────────────────┤
│  Skill Installer                                │
│  ├── Default: Homebrew (brew) → Mac/Linux only  │
│  ├── Alternative: npm/pnpm/bun → Node packages  │
│  └── System deps: git, python, ffmpeg, gh...   │
└─────────────────────────────────────────────────┘
                    ↓
        Windows: No Homebrew, No pnpm?
                    ↓
              INSTALL FAILED

The problem compounds when you choose pnpm as your Node package manager. On Windows, pnpm sometimes isn’t properly added to PATH, causing the “not recognized” error even if it’s installed.

3. The Solution

3.1 Install System Dependencies via winget

Windows has its own package manager: winget. Open PowerShell as Administrator and run:

# Enable script execution first
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

# Install required system tools
winget install Git.Git
winget install ffmpeg
winget install GitHub.cli
winget install Python.Python.3

3.2 Configure OpenClaw to Use npm

The key insight: npm has the best Windows compatibility among Node package managers. pnpm and bun can have PATH issues on Windows.

Find your OpenClaw config file and change the package manager:

{
  "packageManager": "npm",
  "preferredInstallMethod": "winget"
}

If you can’t find the config file, ask the OpenClaw agent directly: “Change my package manager to npm instead of pnpm.”

3.3 Verify Your Installations

Run these commands to confirm everything works:

git --version
python --version
node --version
ffmpeg -version
gh --version

You should see version numbers for each command. If any fail, that tool isn’t in your PATH.

4. The WSL Alternative

Some OpenClaw skills have Linux-specific dependencies that won’t work on native Windows. For maximum compatibility, run OpenClaw inside WSL (Windows Subsystem for Linux).

wsl --install

Then inside WSL (Ubuntu by default):

sudo apt update
sudo apt install git ffmpeg gh python3 python3-pip nodejs npm

This gives you a Linux environment where Homebrew can actually be installed, and all skills work as expected.

5. Comparison: Native Windows vs WSL

┌─────────────────────┬──────────────────┬───────────────────┐
│ Aspect              │ Native Windows    │ WSL                │
├─────────────────────┼──────────────────┼───────────────────┤
│ Setup complexity    │ Lower             │ Higher             │
│ Skill compatibility  │ Good (not 100%)   │ Excellent (100%)   │
│ Performance         │ Native            │ Slight overhead    │
│ Package manager     │ winget + npm      │ apt + brew + npm   │
│ Homebrew support    │ No                │ Yes                │
└─────────────────────┴──────────────────┴───────────────────┘

6. Common Mistakes to Avoid

Choosing pnpm or bun on Windows - Stick with npm for best compatibility
Not restarting PowerShell after installs - PATH won’t update until you do
Skipping system dependencies - git, python, and ffmpeg are needed by many skills
Antivirus blocking - Some antivirus tools block winget downloads; add exceptions if needed

7. Summary

OpenClaw skill installation on Windows fails because it defaults to Homebrew (Mac-only). The fix is straightforward:

Use winget for system packages (git, python, ffmpeg, gh)
Use npm (not pnpm/bun) as your Node package manager
For full compatibility, run OpenClaw inside WSL

The root cause is an assumption in OpenClaw’s architecture that expects Unix-like systems. Windows users need to manually bridge that gap.

Final Words + More Resources

My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me

Here are also the most important links from this article along with some further resources that will help you in this scope:

Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!