Install OpenClaw on Windows

Windows has three supported starting points: the native Windows Hub app, the PowerShell CLI installer, or a WSL2 Gateway. Choose one primary environment and keep its configuration, terminal, and service together.

Option 1: PowerShell installer

Open PowerShell and run:

iwr -useb https://openclaw.ai/install.ps1 | iex

Then complete onboarding:

openclaw onboard --install-daemon

Native Windows installs use a Scheduled Task first, with a per-user Startup-folder fallback when task creation is denied.

Option 2: Windows Hub

Windows Hub provides setup, tray status, chat, node mode, and local MCP features in a desktop interface. It is a good choice when you want a native UI and do not need a Linux-first workflow.

Option 3: WSL2

Use WSL2 when the rest of your agent tooling already lives in Linux. Run the macOS/Linux installer inside the WSL distribution, not in PowerShell, and keep the Gateway service inside that same environment.

Verify the chosen environment

Run these commands in the same shell where you installed OpenClaw:

openclaw --version
openclaw doctor
openclaw gateway status

Expected result

The CLI resolves in that shell, doctor finds no blocking issue, and the Gateway runtime is running. If PowerShell finds the command but WSL does not—or the reverse—you likely installed into only one environment. That is expected; pick the environment you intend to operate.