What the installer needs
The current official requirement is a supported Node runtime: 22.22.3+, 24.15+, or 25.9+. The hosted installer can provision Node when it is missing. Windows supports a native Hub, a PowerShell CLI/Gateway path, and WSL2; choose based on whether you want a desktop companion or a Linux-compatible Gateway.
- Back up an existing OpenClaw state directory before changing install methods.
- Treat installer scripts as privileged code: read the official source and confirm the domain before running.
- Keep provider keys and channel tokens out of shell history; onboarding supports secret-aware flows.
Verify before adding channels
- 1
Confirm the CLI
The command should print an installed version.
openclaw --version - 2
Inspect health
Start in read-only mode. Review findings before any repair.
openclaw doctor - 3
Check the Gateway
Confirm service state and expected endpoint before pairing a channel.
openclaw gateway status
Common questions
Before you act
Does this site install OpenClaw for me?
No. It produces a plan and copyable commands. Nothing is executed, uploaded, or connected from this site.
Should Windows users choose native Windows or WSL2?
Use Windows Hub for the companion experience, PowerShell for a native CLI/Gateway, or WSL2 when you want the closest Linux runtime. The planner explains the trade-off.
Primary sources
Verify against the owner.
Content snapshot follows official docs main at the recorded commit; the current package metadata reported 2026.8.1 when verified. Your installed release and live CLI schema remain authoritative.