OpenClaw on Windows: Detailed Beginner Install Guide
Goal: install OpenClaw from the official openclaw.ai site, finish only the setup needed for one working chat, and postpone advanced channels, memory imports, hooks, plugins, MCP, and remote access until the agent is running.
Best beginner path: use Windows Hub from the official OpenClaw site. Current OpenClaw docs describe Windows Hub as the recommended/easiest Windows desktop path. PowerShell CLI and WSL2 remain supported, but they are fallback or advanced paths for this guide.
Step 01
Before you start
- Use Windows 10 20H2 or newer, or Windows 11.
- Use x64 for most PCs; use ARM64 only for Windows-on-ARM PCs.
- Have reliable internet and permission to run a downloaded user app.
- Set aside 20–30 minutes and keep this guide open.
- Have a model provider ready, or use AgentLens in Step 5 to choose one.
- Keep provider logins/API keys private.
- Do not paste passwords, keys, health, bank, or customer data into test prompts.
- Use the official OpenClaw website first, not a random download link.
Step 02
Choose the easiest Windows path
| Path | Use when | Beginner action |
|---|
| Windows Hub from openclaw.ai | You want a desktop app with setup, tray status, chat, diagnostics, and local pairing. | Use this guide. |
| PowerShell installer | You prefer terminal-first native Windows setup, or official support directs you to it. | Supported alternative; it is not required before Windows Hub. |
| WSL2 Gateway | You intentionally want the Linux-compatible Gateway path. | Supported alternative; it is not required before Windows Hub. |
| GitHub releases | The official site/docs download link sends you there or a download 404s. | Fallback download host only. |
Step 03
Install Windows Hub from the official release
- Open the latest stable Windows Hub release.
- Choose OpenClawCompanion-Setup-x64.exe for most PCs or OpenClawCompanion-Setup-arm64.exe for Windows on ARM.
- If Windows warns about the download, confirm the publisher/source and exact filename. Continue only if you initiated this official download.
- Run the installer. Current docs say Windows Hub installs per user without administrator privileges.
- Open OpenClaw Companion from the Start menu or system tray.
If a direct asset link fails, use the official Windows documentation and follow its Windows Hub release link. Do not use third-party download sites.
Step 04
First launch: make the setup choices
On first launch, Windows Hub may show setup because no usable Gateway is saved yet. Choose the simplest safe options below.
| If OpenClaw asks about… | Choose this first | Why |
|---|
| Gateway location | Set up locally | Hub provisions an app-owned OpenClawGateway WSL distro and pairs the app. It does not export or modify an existing Ubuntu distro. |
| Advanced setup / remote Gateway | Skip / do not choose | Use only if you already have a Gateway URL, token, setup code, WSL Gateway, or SSH tunnel. |
Security gate: continue only with the signed app and local setup you intentionally started. Keep Gateway authentication enabled. Do not approve remote access or broad device permissions just to bypass an error.
- Choose Set up locally.
- Let Windows Hub download and prepare what it needs.
- If it provisions OpenClawGateway, wait; do not close the installer.
- Do not manually install Ubuntu unless support or an advanced WSL guide tells you to.
- Select one AI connection when prompted and wait for its live completion check to pass.
- When setup finishes, look for OpenClaw in the tray. A healthy/green status is the target.
Step 05
Add one model provider safely
- Review the detected connections and supported providers, then explicitly select one you recognize. Detection is read-only and does not authorize or select a provider for you.
- Complete only the login, OAuth, device-code, or API-key flow shown for that selected provider.
- If a browser or device-code page appears, continue only because you initiated it from OpenClaw. Never share the code or approve a sign-in sent by someone else.
- If using an API key, paste it only into the official provider setup field—never a normal chat, screenshot, or support message.
- Wait for the live completion check. A failure does not automatically switch providers; retry or explicitly choose another connection.
- If you need help choosing, use SAGE9AI AgentLens before entering credentials.
Choices
Optional choices to skip until chat works
If these choices appear during onboarding, make the beginner-safe choice now and return later from settings or by asking your running agent.
| Choice | Beginner action | Plain-English reason |
|---|
| Channels / communications | Skip for now | Telegram, Slack, Discord, Teams, Signal, SMS, Matrix, and similar channels add credentials and access control. |
| Memory import | Skip unless you recognize the source | Only import memories from tools you trust. You can import later. |
| Hooks / webhooks | Skip for now | Hooks accept outside events. Enable later with strict tokens and tool policy. |
| Plugins / MCP / local tools | Skip for now | Useful after the agent works, but not required for the first reply. |
| Remote access | Skip for now | Remote Gateway access needs URL/token/network choices. |
| Permissions / screen / camera / system | Only approve what you need | Start with chat. Add sensitive capabilities one at a time later. |
Step 06
Verify connection and send one safe first message
- Open Command Center from the tray.
- Confirm Windows Hub is connected to its local Gateway.
- Open chat and send: Reply with one sentence confirming that the model connection works. Do not change files, connect accounts, or send messages.
- Wait for one normal reply before adding channels, memory imports, hooks, plugins, MCP, screen/camera, or remote access.
The install is complete when the live model test passes, Command Center shows the local connection working, and the message receives a normal reply.
Step 07
If Windows Hub does not work
- Close and reopen OpenClaw Companion from the Start menu.
- Open Command Center diagnostics and read the first error shown.
- Restart the PC if setup was interrupted.
- Check the official Windows documentation.
- If Hub still fails, try the official PowerShell CLI installer:
iwr -useb https://openclaw.ai/install.ps1 | iex
If you manage Node manually, current OpenClaw requires Node 24.16+ or 26.1+, with Node 26 recommended. Do not install Node manually for the Windows Hub path unless official troubleshooting directs you to do so.
Checklist
Beginner success checklist
- I started from openclaw.ai or official Windows docs.
- I installed Windows Hub / OpenClaw Companion.
- I chose local setup instead of advanced setup.
- I chose or connected one model provider.
- I received one useful OpenClaw reply.
- I skipped channels, hooks, plugins, MCP, and remote access for now.
- I did not paste secrets into random tools or chat messages.
- I know Hub may use OpenClawGateway/WSL behind the scenes.
- I know PowerShell CLI is a fallback, not the easiest path.
- I will ask the running agent before adding advanced setup.
Pro Tip:Once your basic agent is up and running, it can install, configure, and set up anything else you would like within the agent harness. No need to guess or research how to do it, because your agent already knows. Just ask it. For safety, tell it to explain the plan before making changes, connecting accounts, or sending messages.
Sources checked
Official sources checked: Windows, Install, and Onboarding Wizard. Key facts: Windows Hub is recommended for Windows 10 20H2+/11 and has signed x64/ARM64 per-user installers; Set up locally provisions an app-owned OpenClawGateway WSL distro without modifying an existing Ubuntu distro; the user explicitly selects one AI connection and a live completion verifies it; PowerShell and WSL2 remain alternatives.
