How to Install OpenClaw on Windows

OpenClaw is a powerful tool for building AI workflows, but setting it up on Windows can be confusing for beginners. This guide walks you through the main installation methods so you can get started quickly.

Table of contents

• OpenClaw Windows installation: 3 methods compared
• What you need before installing OpenClaw on Windows locally
• Method 1: Install OpenClaw on Windows using PowerShell
• Method 2: Install OpenClaw on Windows with WSL2
• Method 3: Run OpenClaw on Windows with Kimi Claw (no setup required)
• Windows firewall and security settings for OpenClaw
• Common OpenClaw installation errors on Windows and how to fix them
• Conclusion

OpenClaw Windows installation: 3 methods compared ​

Before diving into the steps, here is a quick overview of the three ways to install OpenClaw on Windows. Each method has different trade-offs in terms of setup time, feature coverage, and technical requirements.

Kimi Claw is an online tool that lets you run OpenClaw in your browser. It handles setup and configuration automatically, so you do not need Node.js, WSL, or API key setup. You can start using a ready-to-use agent within minutes.

For a local PowerShell or WSL2 setup, scroll down to Method 1 or Method 2. To skip local installation entirely, jump to Method 3: Kimi Claw. If you want to get started faster, you can begin right away.

What you need before installing OpenClaw on Windows locally ​

If you plan to install OpenClaw locally, make sure your system meets the following requirements. If you choose the cloud option like Kimi Claw, you can skip this section entirely.

System requirements ​

• Windows 10 or Windows 11 (64-bit)
• At least 4 GB RAM (8 GB recommended for stable npm builds)
• Stable internet connection
• Administrator privileges for initial setup if you choose WSL2
• For OpenClaw WSL2: virtualization must be enabled in BIOS/UEFI

Required software ​

• Node.js 22 or higher. OpenClaw requires a modern Node.js runtime. Download it from nodejs.org or install via the onboarding script.
• Git for Windows (optional but recommended). Some npm packages and skills depend on Git.

Method 1: Install OpenClaw on Windows using PowerShell ​

Compared to WSL2, the PowerShell method requires fewer steps and no Linux environment. A single command downloads OpenClaw, checks your Node.js version, and launches the onboarding wizard. This method works on both Windows 10 and Windows 11.

Step 1: Install and run your OpenClaw ​

Windows restricts script execution by default to protect your system. Before installing OpenClaw, you must allow PowerShell to execute local scripts by running this "safety switch" command:

Then, run the following command:

After running the command, you should see output similar to the screenshot below. Close and reopen PowerShell to refresh your system PATH before proceeding to onboarding.

Step 2: Ensure risky note & select onboarding mode ​

Select Yes to acknowledge the risk and continue.

Next, select QuickStart to quickly start onboarding. You can adjust settings later, or choose Manual for full configuration.

Step 3: Configure and authenticate your AI model ​

1. Select Moonshot AI as model/auth provider

2. Authenticate and configure your AI model

To connect OpenClaw, activate your Kimi API Key via the Kimi Platform. While a $5 recharge earns you a $5 bonus voucher, we recommend $20+ to unlock Tier 2 access. This reduces latency and ensures that your OpenClaw agent handles complex, multi-step tasks.

3. Create a Kimi API key

Access the API Keys section and click Create API Key. Note that you should keep your API Key in a secure and accessible place. It only shows once when you create it.

4. Enter your API key and select the default model

When the onboarding wizard prompts you, paste your unique API key into the PowerShell/Terminal window.

When asked to choose a default model, select moonshot/kimi-k2.5 (or choose "Keep current" if it's already highlighted). This model provides the best balance of speed and reasoning for agentic tasks.

Step 4: Select channel ​

Choose which app you want to connect to your OpenClaw. If you have no idea, just skip it.

Step 5: Configure for Performance ​

Step 6: Enable Hooks ​

Choose a method to chat with your bot, then wait for it to start running.

Step 7: Run Your OpenClaw ​

After all the above is done, enjoy your OpenClaw.

Method 2: Install OpenClaw on Windows with WSL2 ​

OpenClaw WSL2 setup provides a full Linux environment inside Windows, which is the officially recommended way to run OpenClaw. This method gives you access to the complete feature set, including systemd daemon management, native shell scripting, and smoother npm builds. If you plan to use OpenClaw on Windows for daily workflows or development, OpenClaw WSL is the best choice.

Step 1: Enable WSL2 for OpenClaw on Windows 11/10 ​

Open PowerShell as Administrator and run:

This command enables WSL, downloads Ubuntu, and installs it. After the process completes, restart your computer. When Windows reboots, Ubuntu will launch and ask you to create a username and password.

If you already have WSL installed, verify it is running version 2:

Step 2: Configure WSL2 for systemd ​

OpenClaw runs as a background service using systemd. Enable it in your WSL configuration:

Then restart WSL from PowerShell:

Reopen your Ubuntu terminal and verify systemd is running:

The output should show systemd. If it shows init instead, double-check your /etc/wsl.conf file.

Step 3: Install Node.js 22+ ​

OpenClaw requires Node.js 22 or later. Install it from the NodeSource repository:

Verify the installation:

Step 4: Install OpenClaw via npm ​

With Node.js ready, install OpenClaw globally:

Alternatively, use the official installer script:

Verify the installation:

Step 5: Complete OpenClaw Windows setup via onboarding ​

Run the onboarding wizard using the daemon flag to set up OpenClaw as a systemd service:

The wizard will guide you through:

• Selecting your LLM provider and entering your API key
• Choosing a default model
• Configuring messaging channels (optional)
• Installing the gateway as a background service

After onboarding, enable service persistence, so OpenClaw starts automatically when WSL boots:

The gateway is the core background service that handles all OpenClaw operations, including agent requests, messaging, and model execution. Ensuring it is running confirms that your OpenClaw installation is complete and ready for use, and prevents errors in subsequent steps.

Run the following command in your PowerShell or WSL terminal to check its status:

Method 3: Run OpenClaw on Windows with Kimi Claw (no setup required) ​

If managing Node.js, WSL, and API keys feels like more setup than you need, Kimi Claw offers a simpler way to run OpenClaw. It lets you run OpenClaw directly in your browser without local setup or manual configuration. To get started, follow these steps:

Step 1: Open Kimi Claw and create an instance ​

Go to the Kimi Claw page and click Create to start.

Step 2: Start the deployment ​

Confirm the deployment in the pop-up. Kimi Claw sets up your OpenClaw environment in about two minutes, including the gateway, workspace, and tools. No commands or manual configuration are required.

Step 3: Work in your workspace ​

Once deployment finishes, your workspace opens in the dashboard. You can start chatting with your AI agent, set up skills, configure scheduled tasks, and manage files all from the browser.

What you get with Kimi Claw ​

• Zero configuration: No Node.js, WSL, or API key management required
• 40 GB cloud storage: Save reports, datasets, and generated files that persist across sessions
• Persistent memory: Your AI agent remembers past interactions, preferences, and context
• 5,000+ ClawHub skills: Access automation, research, coding, and analysis skills instantly
• Scheduled task automation: Set up recurring tasks like daily reports, reminders, and monitoring
• Works from any device: Access your OpenClaw agent from any browser on Windows, Mac, or mobile

Windows firewall and security settings for OpenClaw ​

Kimi Claw automatically handles security and networking on cloud servers. If you prefer to install OpenClaw locally with PowerShell or WSL2, there are a few recommended security settings to configure after installation.

• Configuring Windows Firewall

When the OpenClaw gateway starts for the first time, Windows Firewall may prompt you to allow network access. Allow it for private networks only. If you are using OpenClaw WSL2, the gateway runs inside the Linux environment and communicates through localhost, so additional firewall rules are usually not needed.

If Browser Relay or other features cannot connect, make sure that localhost traffic is not being blocked by third-party security software such as antivirus programs, VPN clients, or corporate firewalls.

• Securing the Control UI

The OpenClaw Control UI runs on port 18789 and provides full access to your agent. Never expose this port to the public internet. Keep the gateway bound to 127.0.0.1 and access it only from your local machine.

For secure remote access, use Tailscale to create a private network tunnel:

This keeps the port on localhost while making it accessible through your private Tailscale network.

Common OpenClaw installation errors on Windows and how to fix them ​

Even with a clear guide, you may run into issues during installation. Below are the most frequently reported problems when installing OpenClaw on Windows and how to fix them.

OpenClaw is not recognized ​

• Cause: The npm global bin directory is not in your system PATH.
• Fix: Run the following command to find your npm prefix

Add the output path with \bin appended to your Windows environment variables. Then close and reopen PowerShell.

Git not found during installation ​

• Cause: Git for Windows is not installed.
• Fix: Download and install Git from git-scm.com. After installation, restart PowerShell and retry the OpenClaw Windows installer.

Node.js version is too old ​

• Cause: Your system has an older version of Node.js that does not meet the minimum requirement (v22+).
• Fix: Download the latest LTS version from nodejs.org and install it. If you are using OpenClaw WSL2, reinstall via the NodeSource repository.

Permission denied errors ​

• Cause: PowerShell does not have sufficient permissions, or the npm global directory is not writable.
• Fix: Run PowerShell as Administrator, or change the npm global prefix to a user-writable directory

Gateway won't start ​

• Cause: Port 18789 is already in use, or the configuration file is corrupted.
• Fix: Check for conflicting processes and restart

WSL2 systemd not working ​

• Cause: The /etc/wsl.conf file is missing the systemd configuration.
• Fix: Verify the file contains the correct settings

If the setting is missing, add it and restart WSL with wsl --shutdown in PowerShell.

Conclusion ​

Installing OpenClaw on Windows can range from a simple script-based setup to a more advanced WSL2 environment, depending on your needs. If you want full control and flexibility, PowerShell and WSL2 are solid options. If you prefer to skip setup and start immediately, Kimi Claw lets you run OpenClaw in your browser without local setup. Choose the approach that fits your workflow and technical comfort level, and you will be ready to get the most out of OpenClaw.