OpenClaw for Windows

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

# 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.

Run OpenClaw as a Windows service:

WSL2 Service

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

# 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

For a ready-to-run install script in your browser (install, config, channels, skills), use the Setup Wizard.

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:

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

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

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)

• 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