OpenClaw for Windows

Complete guide to installing and using OpenClaw (formerly Clawdbot and Moltbot) on Windows

Recommended: OpenClaw runs best on Windows via WSL2 (Windows Subsystem for Linux). Native Windows support is also available, but WSL2 is strongly recommended for best compatibility and performance.

Quick Start (WSL2 - Recommended)

WSL2 provides the best experience on Windows:

Step 1: Install WSL2

If you don't have WSL2 installed:

Install WSL2 
wsl --install

Restart your computer when prompted.

Step 2: Install OpenClaw in WSL2

Open WSL2 terminal and run:

Install in WSL2 
curl -fsSL https://openclaw.ai/install.sh | bash

Step 3: Onboard

Onboarding 
openclaw onboard --install-daemon

Native Windows Installation

If you prefer native Windows (not recommended):

Requirements

  • Windows Version: Windows 10 or later
  • Node.js: Node.js ≥22
  • PowerShell: PowerShell 5.1 or later

Installation

Native Windows Install 
# Install Node.js first if needed
# Then install OpenClaw
npm install -g openclaw@latest

# Run onboarding
openclaw onboard

Note: Some features may have limited support on native Windows. WSL2 is strongly recommended.

Windows Service

Run OpenClaw as a Windows service:

WSL2 Service

In WSL2, use systemd (if available) or run manually:

WSL2 Service 
# In WSL2
openclaw onboard --install-daemon

Native Windows Service

For native Windows, you can use NSSM (Non-Sucking Service Manager) or Task Scheduler:

  • Use Task Scheduler to run on startup
  • Or use NSSM to create a Windows service

Accessing Gateway from Windows

WSL2 Gateway Access

If Gateway runs in WSL2, access it from Windows:

  • Get WSL2 IP: wsl hostname -I
  • Access Gateway at: http://<WSL2-IP>:18789
  • Or use port forwarding from WSL2 to Windows

Port Forwarding

Forward WSL2 port to Windows:

Port Forward 
netsh interface portproxy add v4tov4 listenport=18789 listenaddress=0.0.0.0 connectport=18789 connectaddress=<WSL2-IP>

Windows-Specific Features

File System Access

  • WSL2 can access Windows files at /mnt/c/
  • Windows can access WSL2 files via \\wsl$\
  • Workspace can be shared between Windows and WSL2

Windows Terminal

Use Windows Terminal for best WSL2 experience:

  • Better terminal emulation
  • Multiple tabs
  • Better WSL2 integration

Troubleshooting Windows Issues

WSL2 Not Starting

If WSL2 doesn't start:

  1. Enable WSL2 in Windows Features
  2. Enable Virtual Machine Platform
  3. Restart computer
  4. Run: wsl --update

Can't Access Gateway

If you can't access Gateway from Windows:

  1. Check WSL2 IP: wsl hostname -I
  2. Verify Gateway is running: wsl openclaw status
  3. Check Windows Firewall
  4. Set up port forwarding

Performance Issues

If performance is slow:

  1. Ensure WSL2 is used (not WSL1)
  2. Allocate more RAM to WSL2
  3. Store workspace in WSL2 filesystem (not Windows)

Best Practices for Windows

  • Use WSL2 - Best compatibility and performance
  • Store Workspace in WSL2 - Better performance
  • Use Windows Terminal - Better experience
  • Set Up Port Forwarding - Access Gateway from Windows
  • Keep WSL2 Updated - Latest features and fixes

Next Steps