About This Guide: This is an advanced setup guide for running OpenClaw on Windows 11 using the WSL2 (Windows Subsystem for Linux 2) method — officially recommended by the OpenClaw team for maximum compatibility. We also cover PowerShell automation scripts to launch OpenClaw at startup as a background daemon. Estimated time: 30–45 minutes.
OpenClaw is a rapidly growing open-source personal AI assistant that as of February 2026 has surpassed 100,000 GitHub stars. Unlike cloud-locked AI tools, OpenClaw runs on your own hardware — giving you full ownership of your data, conversations, and automation workflows. It integrates with WhatsApp, Telegram, Discord, Slack, iMessage, and Signal, and connects to AI providers including Anthropic Claude, OpenAI GPT-4, and Google Gemini.
The OpenClaw documentation explicitly recommends WSL2 as the primary installation method for Windows, noting that native Windows installation is "untested and more problematic." This guide shows you the right way: WSL2 with Ubuntu, plus PowerShell automation for seamless background operation. Whether you want a 24/7 AI agent running silently on your gaming PC, work laptop, or home server — this is the definitive guide.
Why WSL2 Over Native Windows?
Native Windows (Not Recommended)
- ❌ PowerShell execution policy conflicts
- ❌ Node.js PATH issues with npm global binaries
- ❌ File permission problems in the gateway
- ❌ Poorer tool compatibility for bash-based skills
- ❌ Officially marked "untested" by OpenClaw team
WSL2 Ubuntu (Official Method)
- ✅ Full bash/shell skill compatibility
- ✅ Identical to native Linux experience
- ✅ Node.js PATH works perfectly
- ✅ Systemd support for auto-start daemon
- ✅ Officially supported and tested
System Requirements
Step 1: Enable WSL2 on Windows 11
Open PowerShell as Administrator (right-click the Start menu → Windows Terminal (Admin) or PowerShell (Admin)) and run:
# Enable WSL2 with Ubuntu in one command
wsl --install
# If WSL is already installed, set default version to 2
wsl --set-default-version 2
# Verify WSL2 is active
wsl --status
Restart Required
After running wsl --install, Windows will prompt you to restart. Save all open work and restart your PC. After restart, Ubuntu will automatically install and ask you to create a username and password.
Set Up Ubuntu User Account
After restart, Ubuntu opens automatically. Create your Linux user:
# Ubuntu will prompt for:
Enter new UNIX username: yourname
New password: ••••••••
Retype new password: ••••••••
# Update system packages
sudo apt update && sudo apt upgrade -y
Step 2: Install Node.js 22 via NVM in WSL2
Inside your Ubuntu WSL2 terminal, install nvm (Node Version Manager) — the best way to manage Node.js versions on Linux:
# Install nvm
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.1/install.sh | bash
# Reload shell configuration
source ~/.bashrc
# Install Node.js 22 LTS (required for OpenClaw)
nvm install 22
nvm use 22
nvm alias default 22
# Verify installation
node --version # Should show v22.x.x
npm --version # Should show 10.x.x
Why Node 22? OpenClaw requires Node.js 22+ for its latest features. The nvm approach lets you switch versions easily and avoids permission issues common with system-wide npm installs.
Step 3: Install OpenClaw in WSL2
Now install OpenClaw using the official one-line installer. This automatically handles all dependencies:
Method 1: Official One-Line Installer (Recommended)
# Official installer (handles Node.js + OpenClaw)
curl -fsSL https://openclaw.ai/install.sh | bash
# Start onboarding wizard
openclaw onboard --install-daemon
The installer detects your WSL2 Ubuntu environment and configures everything automatically. The --install-daemon flag sets up OpenClaw to run as a background systemd service.
Method 2: npm Global Install
# Install globally
npm install -g openclaw
# Initialize your agent
openclaw init my-agent
cd my-agent
openclaw onboard
Onboarding Wizard: What to Answer
Step 4: PowerShell Auto-Start on Windows Boot
To make OpenClaw start automatically every time Windows boots (even before any user logs in), create a PowerShell startup script using Windows Task Scheduler:
# Create a startup script file
$scriptContent = @'
wsl -d Ubuntu -u yourname -- bash -c "cd ~/my-agent && openclaw gateway start &"
'@
$scriptPath = "$env:USERPROFILE\openclaw-start.ps1"
Set-Content -Path $scriptPath -Value $scriptContent
# Register as scheduled task (runs at system startup)
$action = New-ScheduledTaskAction -Execute "powershell.exe" `
-Argument "-WindowStyle Hidden -File `"$scriptPath`""
$trigger = New-ScheduledTaskTrigger -AtStartup
$settings = New-ScheduledTaskSettingsSet -Hidden
Register-ScheduledTask -TaskName "OpenClawWSL2" `
-Action $action -Trigger $trigger `
-Settings $settings -RunLevel Highest -Force
Using systemd Inside WSL2 (Alternative)
If WSL2 systemd is enabled (Windows 11 22H2+), you can manage OpenClaw as a proper Linux service:
# Enable systemd in WSL2 (add to /etc/wsl.conf)
echo -e "[boot]\nsystemd=true" | sudo tee /etc/wsl.conf
# After restarting WSL, register OpenClaw service
openclaw gateway install-service
sudo systemctl enable openclaw
sudo systemctl start openclaw
# Check status
sudo systemctl status openclaw
Verify OpenClaw is Running
openclaw gateway status
openclaw dashboard
# Expected output:
# Gateway: Running on port 18789
# Agent: Online
# Memory: Loaded
Step 5: Network Optimization for OpenClaw
OpenClaw makes constant API calls to AI providers and messaging platforms. Network latency and ISP throttling are the #1 cause of OpenClaw performance issues on Windows. Here's how to ensure rock-solid connectivity:
VPN07 — Best Network Partner for OpenClaw
VPN07's 1000Mbps channels eliminate API timeouts that slow down OpenClaw's tool calls. When your agent needs to fetch real-time data, send messages, or call AI models repeatedly, every millisecond counts. 70+ server locations means you can always connect to the nearest AI provider endpoint.
Configure VPN in WSL2
WSL2 shares Windows' network stack, so your VPN connection in Windows automatically applies to OpenClaw running in WSL2. No extra configuration needed — just connect VPN07 in Windows and OpenClaw benefits instantly.
# Test API connectivity from WSL2
curl -w "%{time_total}" -o /dev/null -s https://api.anthropic.com
# With VPN07: typically <50ms response
# Without VPN: 200-800ms or timeout
Advanced: Running Multiple OpenClaw Agents
One powerful advantage of WSL2 is running multiple independent OpenClaw agents simultaneously — one for work, one for personal tasks, one for automation:
Agent 1: Work Agent (Slack + Claude)
openclaw init work-agent --port 18789
cd work-agent && openclaw onboard
Agent 2: Personal Agent (WhatsApp + GPT-4)
openclaw init personal-agent --port 18790
cd personal-agent && openclaw onboard
WSL2 Memory Management
By default WSL2 can consume up to 50% of your RAM. For running multiple agents, create a .wslconfig file in your Windows user folder:
# File: C:\Users\YourName\.wslconfig
[wsl2]
memory=6GB # Limit WSL2 to 6GB RAM
processors=4 # Use 4 CPU cores
swap=2GB # Add 2GB swap
Troubleshooting Common WSL2 + OpenClaw Issues
Error: "WSL2 is not supported on this system"
Cause: CPU virtualization is disabled in BIOS
Fix: Restart PC → Enter BIOS/UEFI → Enable "Intel VT-x" or "AMD-V" → Save and reboot
Error: "openclaw: command not found"
Cause: nvm not loaded or PATH not updated
source ~/.bashrc
nvm use 22
which openclaw # Should show path
OpenClaw API calls timing out
Cause: ISP throttling or poor routing to AI provider servers
Fix: Connect VPN07 on Windows. WSL2 automatically uses the Windows VPN connection. VPN07's 1000Mbps ensures zero throttling on API calls to Anthropic, OpenAI, and Google.
WSL2 memory not being released
Cause: Linux memory caching behavior
# Force release cached memory
sudo sh -c 'echo 3 > /proc/sys/vm/drop_caches'
Power Your OpenClaw with VPN07
OpenClaw on Windows WSL2 demands a rock-solid network. VPN07 delivers 1000Mbps dedicated bandwidth with servers in 70+ countries — eliminating every API timeout and ISP throttling issue that holds your AI agent back. Trusted by thousands of developers for 10+ years. Start for just $1.5/month with a 30-day money-back guarantee.