How to Install OpenClaw (macOS, Windows, Linux): Clean Setup + Verification

Hey there, automation builders. If you're ready to install OpenClaw but wondering which path to take—CLI install, Docker, or something else—I've run through every major setup route across macOS, Ubuntu, and Windows WSL2.

I'll walk you through the decision points, platform-specific steps, verification checks that actually matter, and how to cleanly uninstall if things go wrong. Here's what worked (and what didn't) across three different machines.

Choose Your Install Path (CLI vs Docker)

When to Use CLI (Local, Lightweight, Dev-First)

Recommended for:

• Personal use on a single machine
• Full system access (file operations, browser control, local automations)
• Faster iteration and debugging
• Lowest setup friction

Advantages:

• Direct access to Gateway logs (openclaw gateway logs)
• One-command install: npm install -g openclaw@latest
• Onboarding wizard handles daemon setup automatically
• Easier skill installation and configuration

Setup time: 5-10 minutes if you have Node.js 22+ already installed.

Cuándo Usar Docker (Aislado, Reproducible, Más Seguro)

Recomendado para:

• Despliegues en servidores o alojamiento VPS
• Entornos compartidos donde se desea aislamiento
• Ejecutar múltiples instancias de OpenClaw en un solo host
• Configuraciones sensibles a la seguridad (modo sandbox habilitado por defecto)

Ventajas:

• Aislamiento por sesión para automatizaciones de grupo/canal
• Construcciones reproducibles en diferentes entornos
• Más fácil de desmantelar y reconstruir
• Sin conflictos de versión de Node.js

Tiempo de configuración: 10-15 minutos incluyendo la instalación de Docker y la descarga de la imagen.

Según la documentación oficial de OpenClaw, las instalaciones basadas en Docker soportan el modo Nix para configuración declarativa y sandboxes por sesión.

Atajo de Decisión para Principiantes

Instalación en macOS

Requisitos Previos (Homebrew, Permisos)

Verificar versión de Node.js:

node --version
# Must show v22.x.x or higher

If you don't have Node 22+, install via Homebrew:

brew install node@22
brew link node@22

Or use nvm:

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.1/install.sh | bash
nvm install 22 && nvm use 22

CLI Install Steps

# Install OpenClaw globally
npm install -g openclaw@latest
# Verify installation
openclaw --version
# Should show: openclaw/2026.1.29
# Run onboarding wizard (installs launchd daemon)
openclaw onboard --install-daemon

What --install-daemon does:

• Creates launchd service at ~/Library/LaunchAgents/com.openclaw.gateway.plist
• Auto-starts Gateway on login
• Runs Gateway in background (you don't need terminal open)

Docker Install Alternative

# Pull latest image
docker pull openclaw/openclaw:latest
# Run with volume mounts for config persistence
docker run -d \
  --name openclaw-gateway \
  -v ~/.openclaw:/root/.openclaw \
  -p 18789:18789 \
  openclaw/openclaw:latest \
  gateway --port 18789

Per GitHub issue #1679, Docker deployments require explicit auth token configuration when accessed via reverse proxy.

Default Config & File Locations

~/.openclaw/
├── openclaw.json       # Main config (model, channels, tools)
├── state/              # Session data, message history
├── workspace/          # Skills and custom tools
└── credentials/        # OAuth tokens, API keys
~/Library/LaunchAgents/
└── com.openclaw.gateway.plist  # macOS daemon config

Windows Install (WSL2 Recommended)

Why WSL2 is Required

OpenClaw does not support native Windows. The WhatsApp Web protocol, iMessage integration, and Unix-based process management all assume a POSIX environment.

According to the Windows platform guide, WSL2 (Windows Subsystem for Linux) is the only supported path for Windows users.

WSL2 Setup Checklist

1. Enable WSL2:

# Run in PowerShell as Administrator
wsl --install

This installs Ubuntu 24.04 by default. Restart your computer when prompted.

1. Launch Ubuntu:

• Open "Ubuntu" from Start Menu
• Create username and password when prompted

1. Verify WSL version:

wsl --list --verbose
# Should show VERSION = 2

If it shows VERSION = 1, upgrade:

wsl --set-version Ubuntu 2

OpenClaw Install Inside WSL

Once inside Ubuntu (WSL2), follow the Linux install steps:

# Update packages
sudo apt update && sudo apt upgrade -y
# Install Node.js 22
curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -
sudo apt install -y nodejs
# Verify Node version
node --version
# Install OpenClaw
npm install -g openclaw@latest
# Run onboarding
openclaw onboard --install-daemon

Common Windows-Specific Pitfalls

Issue 1: WSL network access from Windows

By default, WSL2 uses a virtualized network. To access the OpenClaw web dashboard from Windows browser:

1. Find WSL IP:

ip addr show eth0 | grep inet
# Example output: inet 172.20.224.5/20

1. Access dashboard at http://172.20.224.5:18789/ (replace with your WSL IP)

Issue 2: File system performance

Store ~/.openclaw/ inside WSL file system (/home/username/), not Windows (/mnt/c/). Cross-system file access is 10-20x slower.

Issue 3: systemd not running

Some WSL2 distributions don't enable systemd by default. Check:

systemctl --version

If it fails, enable systemd in /etc/wsl.conf:

sudo nano /etc/wsl.conf

Add:

[boot]
systemd=true

Restart WSL:

wsl --shutdown

Linux Install

Supported Distros

Package Dependencies

Ubuntu/Debian:

sudo apt update
sudo apt install -y curl git build-essential

Fedora:

sudo dnf install -y curl git gcc-c++ make

Arch:

sudo pacman -S curl git base-devel

CLI Install Steps

# Install Node.js 22
curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -
sudo apt install -y nodejs
# Or use nvm for user-level install
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.1/install.sh | bash
source ~/.bashrc
nvm install 22 && nvm use 22
# Install OpenClaw
npm install -g openclaw@latest
# Run onboarding (installs systemd service)
openclaw onboard --install-daemon

Running OpenClaw as a Service (Optional)

The --install-daemon flag creates a systemd user service automatically. Verify it's running:

systemctl --user status openclaw-gateway

Expected output:

● openclaw-gateway.service - OpenClaw Gateway
   Loaded: loaded (/home/user/.config/systemd/user/openclaw-gateway.service)
   Active: active (running)

Manual service management:

# Start
systemctl --user start openclaw-gateway
# Stop
systemctl --user stop openclaw-gateway
# Restart
systemctl --user restart openclaw-gateway
# View logs
journalctl --user -u openclaw-gateway -f

Enable auto-start on boot:

systemctl --user enable openclaw-gateway
sudo loginctl enable-linger $USER

The enable-linger command allows user services to start before login, which is necessary for headless servers.

Verify Installation

Check Version Output

openclaw --version

Expected output:

openclaw/2026.1.29

If you see command not found, verify npm global bin is in your PATH:

echo $PATH | grep npm

Add it if missing:

echo 'export PATH="$PATH:$(npm config get prefix)/bin"' >> ~/.bashrc
source ~/.bashrc

Run Health Checks

openclaw doctor

Healthy installation output:

✅ CLI version: 2026.1.29
✅ Node.js: v22.11.0
✅ Gateway service: running (PID 12345)
✅ Config: ~/.openclaw/openclaw.json
✅ Auth: Anthropic API key configured
⚠️  DM policy: pairing (requires approval for unknown senders)
ℹ️  Channels: telegram, whatsapp (2 connected)

Common warnings:

• ⚠️ Gateway exposed on 0.0.0.0 - See security guide
• ⚠️ Auth mode: none - This is removed in v2026.1.29+ (per release notes)

Read Logs Correctly

# View recent Gateway logs
openclaw gateway logs --tail 50
# Follow logs in real-time
openclaw gateway logs --follow

Key log patterns to recognize:

Successful startup:

2026-01-30T12:00:00.000Z [gateway] agent model: anthropic/claude-sonnet-4-5-20250929
2026-01-30T12:00:00.100Z [gateway] listening on ws://127.0.0.1:18789 (PID 12345)
2026-01-30T12:00:00.200Z [canvas] host mounted at http://127.0.0.1:18793/__openclaw__/canvas/

Authentication working:

2026-01-30T12:01:00.000Z [telegram] connected @yourbotname
2026-01-30T12:01:00.100Z [whatsapp] paired device: Chrome (Linux)

Problem indicators:

Error: Missing API key for Anthropic
[ws] unauthorized conn=xxx reason=token_missing
Error: EACCES: permission denied

What "Working" Looks Like

Minimal working test:

1. Send a message to your Telegram bot:

Hello

1. Expected response:

Hello! I'm your OpenClaw assistant. How can I help you today?

1. Check logs show the interaction:

openclaw gateway logs --tail 10

1. Should contain:

[telegram] ← message from @yourusername
[agent] generating response (model: claude-sonnet-4-5)
[telegram] → reply sent

If you see this flow, your installation is working correctly.

Uninstall or Reset Configuration

Full Uninstall Steps

macOS:

# Stop and remove daemon
openclaw gateway stop
launchctl unload ~/Library/LaunchAgents/com.openclaw.gateway.plist
rm ~/Library/LaunchAgents/com.openclaw.gateway.plist
# Remove OpenClaw package
npm uninstall -g openclaw
# Remove config and data (optional)
rm -rf ~/.openclaw

Linux:

# Stop and disable service
systemctl --user stop openclaw-gateway
systemctl --user disable openclaw-gateway
rm ~/.config/systemd/user/openclaw-gateway.service
# Remove package
npm uninstall -g openclaw
# Remove config and data (optional)
rm -rf ~/.openclaw

Windows (WSL2):

Same as Linux steps above, run inside Ubuntu WSL2 terminal.

Resetting Config Without Reinstall

Option 1: Delete config only (preserves session history)

mv ~/.openclaw/openclaw.json ~/.openclaw/openclaw.json.backup
openclaw onboard

Option 2: Full state reset (fresh start)

openclaw gateway stop
mv ~/.openclaw ~/.openclaw.backup
openclaw onboard --install-daemon

Option 3: Reset specific channels

rm ~/.openclaw/credentials/telegram.json
openclaw channels login

When a Clean Reset is the Right Move

Reset if:

• Gateway won't start after config changes
• Channel pairing is broken (WhatsApp QR expired, Telegram token invalid)
• You switched API providers (Anthropic ↔ OpenAI) and seeing auth errors
• Upgrade migration failed (openclaw doctor shows state version mismatch)

Don't reset if:

• You just want to change one setting (edit ~/.openclaw/openclaw.json directly)
• Daemon isn't starting (check systemctl --user status openclaw-gateway first)
• Pairing codes aren't working (run openclaw pairing list to see pending pairs)

I've hit all these scenarios testing across platforms. The most common mistake is resetting config when you just need to restart the daemon—save yourself 10 minutes and check service status first.

Prefer a guided setup? At Macaron, we built an AI that remembers your context and creates personalized mini-apps from a single sentence—no technical setup required. If you want to test how conversation turns into custom tools for daily tasks like meal planning or habit tracking, sign up and run your first automation instantly with Macaron.

FAQ

Q: Do I need Node.js 22+ or can I use an older version?

Node.js 22+ is required. Older versions won't work—you'll get syntax errors immediately.

P: La puerta de enlace muestra "en funcionamiento" pero no puedo acceder al panel de control. ¿Qué sucede?

El enlace predeterminado cambió a solo localhost en la versión v2026.1.29. Accede desde la misma máquina en http://127.0.0.1:18789 o configura Tailscale para acceso remoto.

P: WhatsApp sigue desconectándose y reconectándose. ¿Cómo lo soluciono?

Elimina las credenciales y vuelve a emparejar: rm -rf ~/.openclaw/credentials/whatsapp luego ejecuta openclaw channels login --channel whatsapp nuevamente.

P: El comando openclaw no se encuentra después de la instalación.

Agrega el bin global de npm a tu PATH: echo 'export PATH="$PATH:$(npm config get prefix)/bin"' >> ~/.bashrc && source ~/.bashrc

P: ¿Es seguro exponer la puerta de enlace a internet?

No. Usa Tailscale en su lugar. La exposición directa a internet tuvo múltiples vulnerabilidades críticas en enero de 2026.

P: ¿Puedo ejecutar esto en un Raspberry Pi o un VPS barato?

Sí. Necesita más de 1GB de RAM. Sigue los pasos de instalación para Linux: Docker funciona pero usa más memoria.