Windows install

Three paths.

Pick the one that matches your Windows setup. All three install the same plugin into the same place. OpenClaw must be installed on the same side (native Windows or WSL2) as the install command you run. Replace <your-token> with the token in your post-checkout setup wizard; without it, the scripts install OpenClaw only, not the Clawmont security layer.

Windows support - built and verified to spec.

Every install path here is built and verified against the official Windows PowerShell, npm, and Git for Windows specifications. Questions about your specific setup? Email our team at support@clawmont.com and we'll help you get running.

  1. 01

    PowerShell (native)

    Lightest path. No extra runtime. Works on Windows 10 / 11 with Node 22+, npm, and OpenClaw on PATH. Junction-links into ~/.openclaw/extensions/ - no admin or Developer Mode required.

    $env:CLAWMONT_CONFIG='<your-token>'; irm https://api.clawmont.com/install.ps1 | iex

    Status: Recommended path. Built and verified to the Windows PowerShell and npm specs - no admin or Developer Mode required.

  2. 02

    Git Bash (Git for Windows)

    Same one-liner as macOS / Linux. Bash 5.x ships with Git for Windows so all install.sh features (arrays, set -euo pipefail, &> redirection) work. ln -sf falls back to a copy unless Developer Mode is on.

    curl -fsSL https://api.clawmont.com/install.sh | bash -s -- --config <your-token>

    Status: Verified against the Git for Windows spec. The same one-liner as macOS and Linux.

  3. 03

    WSL2

    Use only when OpenClaw is also installed inside WSL2. If OpenClaw is installed natively on Windows, the symlink lands in the WSL filesystem and Windows-side OpenClaw will not see it.

    curl -fsSL https://api.clawmont.com/install.sh | bash -s -- --config <your-token>

    Status: Supported for OpenClaw running inside WSL2 - not for a native-Windows OpenClaw.

Picking a path

  • Default to PowerShell. Lightest, most native, no extra shell to install.
  • Use Git Bash if you already have Git for Windows installed and prefer the same one-liner the macOS / Linux docs show.
  • Use WSL2 only if your OpenClaw runs inside WSL2 too. Cross-boundary installs (WSL2 install of a Windows-side OpenClaw) won't work - Windows OpenClaw can't see /home/<user>/.openclaw/.