OpenClaw Windows 11: How to Install and Set It Up

Published on: 25/09/2026 | Updated on: September 25, 2026

Yes, you can run OpenClaw on Windows 11. The current OpenClaw documentation supports three Windows approaches: the native Windows Hub companion app, the PowerShell CLI/Gateway installer, and a WSL2 Gateway. Windows Hub is the recommended desktop route, while WSL2 is intended for users who want the most Linux-compatible Gateway environment.

OpenClaw on Windows 11: What You Need to Know First

If you are searching for OpenClaw Windows 11, you will find many guides that start with WSL2. That can be confusing because the current Windows setup has more than one supported path.

OpenClaw now provides a native Windows Hub companion app, a native PowerShell installation, and a WSL2-based Gateway. The right choice depends on whether you want a desktop-first experience, a terminal-first workflow, or a Linux-compatible environment.

OpenClaw’s current installation documentation lists Node.js 24.16+ or 26.1+, with Node 26 recommended. Windows users can also use the Windows Hub, which handles much of the desktop setup for them.

If you are new to AI agents, it may help to first understand how Windows 11 AI agents work before installing OpenClaw.

Can You Run OpenClaw on Windows 11?

Yes. OpenClaw officially supports Windows through three main approaches:

Method	Best for	What you get
Windows Hub	Most desktop users	GUI setup, tray controls, chat and diagnostics
PowerShell	Terminal users	Native Windows CLI and Gateway
WSL2	Linux-oriented users	Linux-compatible Gateway environment

Windows Hub supports Windows 11 as well as Windows 10 20H2 and later. Its installer is available for both x64 and ARM64 systems and does not require administrator privileges.

The important point is that WSL2 is not mandatory for every Windows 11 installation. It remains an important option, but it is no longer the only supported route.

Which OpenClaw Windows 11 Installation Method Should You Choose?

For most Windows desktop users, start with Windows Hub. It provides a normal Windows application experience and can set up an app-owned WSL Gateway during first-run setup.

Choose Windows Hub if you want a desktop app

Windows Hub gives you:

• System tray status
• Launch-at-login support
• First-run setup
• Chat
• Command Center diagnostics
• Gateway connection settings
• Windows node capabilities
• Browser Control UI access

It can also provision its own local WSL Gateway, so you do not necessarily need to manually configure WSL2 first.

Choose PowerShell if you prefer the command line

The native PowerShell route gives you direct access to the OpenClaw CLI and Gateway from Windows.

This is useful if you are comfortable with terminals, scripts, and Windows automation.

Choose WSL2 if you need Linux compatibility

WSL2 is the better fit when you specifically want a Linux-style runtime, Linux-native tooling, systemd services, or a setup closer to how OpenClaw would run on a Linux server. The official documentation describes WSL2 as the most Linux-compatible Gateway runtime on Windows.

The best installation method is therefore not a universal ranking. It depends on how you plan to use OpenClaw.

How to Install OpenClaw on Windows 11 With Windows Hub

For a normal Windows 11 desktop, this is the simplest path to start with.

Download the Windows Hub

OpenClaw provides signed Windows Hub installers for:

• x64 PCs
• ARM64 PCs

The current Windows documentation lists the installer names as OpenClawCompanion-Setup-x64.exe and OpenClawCompanion-Setup-arm64.exe.

Use the installer that matches your Windows architecture.

Install the Windows companion

Run the installer and complete the normal Windows installation process.

The current Hub installs without requiring administrator privileges. After installation, you can launch OpenClaw Companion from the Start menu or system tray.

Complete first-run setup

On first launch, Windows Hub can help configure a local Gateway.

If you do not already have a Gateway, the setup wizard can create an app-owned WSL Gateway. You can also connect the companion to an existing Gateway.

This is one reason Windows Hub can be easier for new Windows users than manually building the entire WSL2 environment.

Use the Command Center

Windows Hub includes Command Center diagnostics for areas such as sessions, channels, nodes, pairing and repair commands.

That gives you a useful place to check the installation before assuming something is broken.

How to Install OpenClaw on Windows 11 With PowerShell

If you prefer a terminal, OpenClaw provides an official PowerShell installer.

Step 1: Open PowerShell

Open PowerShell in Windows 11.

You do not need to begin by manually installing WSL2 if you are using the native PowerShell route.

Step 2: Run the official installer

The current OpenClaw installation documentation provides this command:

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

The installer can detect the Windows environment, ensure a supported Node.js runtime is available, install OpenClaw, and launch onboarding.

Step 3: Let the installer handle Node.js when needed

The current Windows installer supports Node 24.16+ and Node 26.1+. Node 22, 23 and 25 are not supported by the current installer documentation.

If Node.js is missing, the installer can attempt to obtain a supported runtime using available Windows package managers. If those options are unavailable, the installer has a portable Node fallback.

Step 4: Complete onboarding

OpenClaw’s onboarding process configures authentication and helps establish a working Gateway and chat session.

The current getting-started documentation says onboarding can reuse an existing Claude Code or Codex CLI login or use a provider API key when available.

Step 5: Verify the installation

Do not stop immediately after the installer says it has finished.

Check the installed version:

openclaw --version

Then run:

openclaw doctor

And check the Gateway:

openclaw gateway status --json

The verification stage matters because a successful package installation does not automatically prove that your Gateway and authentication are configured correctly. The official installation documentation specifically recommends diagnostic and Gateway checks.

How to Install OpenClaw on Windows 11 With WSL2

WSL2 is useful when you want OpenClaw’s Gateway to operate inside a Linux environment while still using Windows 11 as your main operating system.

Step 1: Install WSL2

Open PowerShell as Administrator and run:

wsl --install

You can also list available distributions:

wsl --list --online

Or install Ubuntu 24.04 explicitly:

wsl --install -d Ubuntu-24.04

These are the current commands documented by OpenClaw for manual WSL2 setup.

Step 2: Enable systemd

Inside your WSL distribution, configure /etc/wsl.conf:

sudo tee /etc/wsl.conf >/dev/null <<'EOF'
[boot]
systemd=true
EOF

Then return to PowerShell and restart WSL:

wsl --shutdown

OpenClaw’s Gateway service can use systemd user services in WSL2.

Step 3: Install OpenClaw inside WSL2

From the Linux environment, use the Linux installer:

curl -fsSL https://openclaw.ai/install.sh | bash

Then check the Gateway:

openclaw gateway status

The important detail is that WSL2 has its own Linux environment. Installing Node.js or OpenClaw in native Windows PowerShell does not install them inside your WSL distribution, and vice versa.

Step 4: Configure automatic startup if needed

If you want a headless WSL setup to start as part of your Windows boot process, OpenClaw documents additional configuration involving systemd lingering and a Windows scheduled task.

This is useful for automation that needs to continue running without manually opening a terminal.

How to Configure OpenClaw After Installation

Installing OpenClaw is only the first part of the process.

A usable setup normally involves:

1. Installing OpenClaw.
2. Completing onboarding.
3. Configuring authentication.
4. Starting or connecting to a Gateway.
5. Opening the dashboard.
6. Connecting the channels or tools you need.
7. Running a simple test task.

OpenClaw’s getting-started documentation describes the goal as reaching a running Gateway, configured authentication and a working chat session.

Choose your AI model access

OpenClaw needs usable AI access. Depending on your setup, onboarding can use an existing supported CLI login or a provider API key.

Keep API credentials private. Do not paste secret keys into public posts, screenshots or support forums.

Configure the Gateway

The Gateway is the central service that allows OpenClaw’s agent functionality to operate.

You can check its status from the CLI:

openclaw gateway status --json

A healthy installation should give you a clear indication of whether the Gateway is running and reachable.

Connect your channels

OpenClaw supports multiple communication channels. The current documentation describes integrations including Telegram, Discord, Slack, WhatsApp and others.

Only connect the channels you actually need.

How to Verify That OpenClaw Is Working

Use this simple diagnostic sequence:

openclaw --version

Then:

openclaw doctor

Then:

openclaw gateway status --json

If those checks are successful, continue to the dashboard and test a simple task.

This approach is better than immediately troubleshooting individual symptoms because it separates three different problems: installation, configuration and Gateway operation.

OpenClaw Windows 11 Troubleshooting

“openclaw” is not recognized

This usually points to a Windows PATH problem.

The official OpenClaw installation documentation identifies PATH as a common reason for the openclaw command not being found.

First check whether the installation completed successfully. Then restart the terminal and check your PATH configuration.

Do not immediately reinstall everything. A PATH problem can make a working installation appear broken.

Node.js version problems

Check your Node version:

node --version

The current OpenClaw documentation supports Node 24.16+ or Node 26.1+, with Node 26 recommended.

Avoid following an older tutorial that tells you to install an unsupported Node release simply because that tutorial was published earlier.

Gateway is not running

Check:

openclaw gateway status --json

Then run:

openclaw doctor

These commands give you more useful diagnostic information than repeatedly restarting the computer.

WSL2 Gateway does not start

If you installed OpenClaw inside WSL2, remember that the Linux environment has its own Node.js and OpenClaw installation.

Check the environment from inside WSL2 rather than checking the Windows installation.

Also verify that systemd is enabled if your Gateway service depends on it. The official Windows documentation specifically includes systemd configuration for manual WSL2 setups.

OpenClaw stops when you close the terminal

This can happen when the Gateway has not been configured as a managed service.

The current installation documentation supports managed startup on native Windows through a Scheduled Task, while Linux/WSL2 uses systemd user services.

The solution depends on which installation architecture you selected.

Windows and WSL2 installations behave differently

This is a common conceptual mistake.

Think of them as separate environments:

Environment	Node.js	OpenClaw
Native Windows	Windows Node	Windows OpenClaw
WSL2	Linux Node	Linux OpenClaw

Updating Node.js in Windows does not automatically update the Node.js installation inside WSL2.

What Can OpenClaw Do on Windows 11?

OpenClaw is designed to operate as an AI agent rather than only as a conventional chatbot.

Depending on your configuration, it can interact with tools, channels and the Windows environment.

The Windows Hub documentation specifically describes Windows node capabilities involving:

• Screen
• Camera
• Notifications
• Device status
• Talk
• Controlled system.run

These capabilities are subject to configuration and policy controls.

The practical value is that an AI agent can potentially move beyond answering a question and interact with the environment where the task needs to happen.

That also makes permissions important.

OpenClaw Windows 11 Security Considerations

An AI agent with access to tools can have more impact than a normal chat window.

Protect your API keys

Treat provider API keys as secrets.

Do not place them in:

• Public GitHub repositories
• Screenshots
• Blog posts
• Public configuration files
• Untrusted scripts

Be careful with Gateway exposure

A Gateway that is only intended for local use should not be casually exposed to the public internet.

Understand whether your Gateway is listening locally, remotely, or through a tunnel before changing network settings.

Give tools only the access they need

If an agent does not need access to a particular tool or Windows capability, do not enable it simply because it exists.

This is especially important for capabilities that can execute commands or interact with files and devices.

Keep your installation updated

OpenClaw is an actively changing project. Installation commands, supported runtimes, integrations and Windows functionality can change.

For that reason, the official documentation should remain the final reference when an older tutorial conflicts with the current installation process.

OpenClaw Windows 11: Common Setup Mistakes to Avoid

Mistake 1: Assuming WSL2 is mandatory

It is not. Current OpenClaw documentation supports Windows Hub, native PowerShell and WSL2.

Mistake 2: Following an outdated Node.js guide

Node compatibility changes over time. Use the current OpenClaw requirement instead of blindly copying a version from an older tutorial.

Mistake 3: Installing OpenClaw in Windows and WSL2 without understanding the difference

That can leave you with two separate environments and two different installations.

Choose your architecture deliberately.

Mistake 4: Skipping Gateway verification

An installation can complete while the Gateway still needs configuration.

Run the diagnostic commands before moving on.

Mistake 5: Giving an AI agent unnecessary permissions

More permissions do not automatically mean a better AI workflow.

Start with the minimum capabilities you need and expand them only when necessary.

OpenClaw Windows 11 FAQ

Can OpenClaw run directly on Windows 11?

Yes. OpenClaw supports Windows 11 through its native Windows Hub companion app and native PowerShell CLI/Gateway. WSL2 is an additional supported option for users who want a Linux-compatible Gateway environment.

Does OpenClaw require WSL2 on Windows 11?

No. WSL2 is not required for every OpenClaw Windows installation. You can use Windows Hub or the native PowerShell installer. WSL2 is particularly useful when you want the most Linux-compatible Gateway runtime.

What is the easiest way to install OpenClaw on Windows 11?

For a desktop-first setup, the current OpenClaw documentation points Windows users toward the native Windows Hub companion app. It provides setup, tray status, chat and diagnostics, and can provision an app-owned WSL Gateway.

What version of Node.js does OpenClaw require?

The current installation documentation lists Node.js 24.16+ or 26.1+, with Node 26 recommended. The current Windows installer documentation says Node 22, 23 and 25 are unsupported.

How do I check whether the OpenClaw Gateway is running?

From the native Windows CLI, run:

openclaw gateway status --json

You can also use openclaw doctor to identify configuration or environment problems.

Can I use OpenClaw on Windows 11 without manually installing Linux?

Yes. Windows Hub provides a Windows desktop experience and can provision its own app-owned WSL Gateway during setup. You do not have to manually build a WSL2 environment before using the Hub.

Why is OpenClaw not recognized in PowerShell?

The official documentation identifies PATH configuration as a common cause. Check whether OpenClaw was installed successfully, restart PowerShell, and verify that the directory containing the OpenClaw executable is available through your user PATH.

Choosing Your OpenClaw Windows 11 Setup

If you want a straightforward Windows desktop experience, start with Windows Hub. If you prefer command-line control, use the PowerShell installation. If your workflow depends on Linux tooling and services, use WSL2.

The key is to choose the environment first and then follow the installation path designed for that environment. That avoids one of the most common OpenClaw Windows problems: mixing native Windows and WSL2 installations without realizing that they are separate runtimes.

Want to explore more? Learn about Microsoft Scout and Use the official OpenClaw Windows documentation as the source of truth for installation commands and Windows-specific changes, because this project is evolving quickly.