openclaw windows install

OpenClaw Installation on Windows (with gateway fixes)

Built for high-intent queries like openclaw windows install and deployment troubleshooting.

Last updated: 2026-03-11

  • Prefer WSL2 on Windows (officially recommended)
  • Node runtime must be >= 22 for source/npm paths
  • Run openclaw onboard --install-daemon after installation
openclaw windowsopenclaw installgateway startup failed

1. Pre-flight checks

For Windows, align with the documented WSL2 path to avoid most bootstrap issues.

  • Windows 10/11 + WSL2 ready
  • Node >= 22 and Git for source/npm install modes
  • Gateway token and model API key stored in env vars

2. Official installation flow on Windows

Use the official PowerShell installer first, then finish onboarding.

  1. Run install.ps1 from openclaw.ai
  2. Execute openclaw onboard --install-daemon
  3. Complete gateway/provider/channel setup in the wizard
  4. Verify health endpoint and a minimal workflow

PowerShell installer + onboarding

# PowerShell\n& ([scriptblock]::Create((iwr -useb https://openclaw.ai/install.ps1)))\n\n# Then\nopenclaw onboard --install-daemon

3. Gateway startup failures

Validate binding/ports and token first, then read gateway logs.

  • Check `127.0.0.1:18789/healthz`
  • Verify `OPENCLAW_GATEWAY_TOKEN` and provider keys
  • Inspect `docker compose logs --since=30m openclaw-gateway`

Frequently asked questions

The dashboard does not load after install. What should I do?

Verify process status first, then check ports, firewall, and proxy chain.

Do I need Docker for Windows setup?

No. Docker is optional; for Windows, the official recommendation is WSL2-based setup.

Sources