diff --git a/docs/platforms/windows.md b/docs/platforms/windows.md index e40d798604d..d0aef529f00 100644 --- a/docs/platforms/windows.md +++ b/docs/platforms/windows.md @@ -1,22 +1,22 @@ --- -summary: "Windows (WSL2) support + companion app status" +summary: "Windows support: native and WSL2 install paths, daemon, and current caveats" read_when: - Installing OpenClaw on Windows + - Choosing between native Windows and WSL2 - Looking for Windows companion app status -title: "Windows (WSL2)" +title: "Windows" --- -# Windows (WSL2) +# Windows -OpenClaw on Windows is recommended **via WSL2** (Ubuntu recommended). The -CLI + Gateway run inside Linux, which keeps the runtime consistent and makes -tooling far more compatible (Node/Bun/pnpm, Linux binaries, skills). Native -Windows might be trickier. WSL2 gives you the full Linux experience — one command -to install: `wsl --install`. +OpenClaw supports both **native Windows** and **WSL2**. WSL2 is the more +stable path and recommended for the full experience — the CLI, Gateway, and +tooling run inside Linux with full compatibility. Native Windows works for +core CLI and Gateway use, with some caveats noted below. Native Windows companion apps are planned. -## Install (WSL2) +## WSL2 (recommended) - [Getting Started](/start/getting-started) (use inside WSL) - [Install & updates](/install/updating) diff --git a/docs/start/getting-started.md b/docs/start/getting-started.md index 381493ed209..22a5fe80914 100644 --- a/docs/start/getting-started.md +++ b/docs/start/getting-started.md @@ -19,7 +19,8 @@ and a working chat session. Check your Node version with `node --version`. -Windows users: WSL2 is strongly recommended. See [Windows](/platforms/windows). +**Windows users:** both native Windows and WSL2 are supported. WSL2 is more +stable and recommended for the full experience. See [Windows](/platforms/windows). Need to install Node? See [Node setup](/install/node). diff --git a/docs/start/onboarding-overview.md b/docs/start/onboarding-overview.md index e3293ba7a59..fe768a8393f 100644 --- a/docs/start/onboarding-overview.md +++ b/docs/start/onboarding-overview.md @@ -14,13 +14,13 @@ optional channels — they just differ in how you interact with the setup. ## Which path should I use? -| | CLI onboarding | macOS app onboarding | -| -------------- | ------------------------------- | ------------------------- | -| **Platforms** | macOS, Linux, Windows (WSL2) | macOS only | -| **Interface** | Terminal wizard | Guided UI in the app | -| **Best for** | Servers, headless, full control | Desktop Mac, visual setup | -| **Automation** | `--non-interactive` for scripts | Manual only | -| **Command** | `openclaw onboard` | Launch the app | +| | CLI onboarding | macOS app onboarding | +| -------------- | -------------------------------------- | ------------------------- | +| **Platforms** | macOS, Linux, Windows (native or WSL2) | macOS only | +| **Interface** | Terminal wizard | Guided UI in the app | +| **Best for** | Servers, headless, full control | Desktop Mac, visual setup | +| **Automation** | `--non-interactive` for scripts | Manual only | +| **Command** | `openclaw onboard` | Launch the app | Most users should start with **CLI onboarding** — it works everywhere and gives you the most control.