Want to run OpenClaw on Windows without interruptions? This guide covers everything you need to install and operate OpenClaw — a Node.js-powered AI assistant — on Windows and keep it running continuously. OpenClaw connects messaging platforms like WhatsApp and Telegram to AI agents for task automation, browser control, calendar management, and more.
Here’s what you’ll learn:
Three deployment options at a glance:
Quick tip: For local setups, disable sleep mode and use a UPS for backup power. For long-term reliability, a VPS or Windows cloud desktop is the better choice.
Before diving into the installation, make sure your system meets OpenClaw’s requirements. OpenClaw supports Windows 10 (version 20H2 or later) and Windows 11, and requires a 64-bit processor — either x64 (Intel/AMD) or ARM64 (Surface Pro X, Snapdragon laptops).
| Prerequisite | Minimum | Recommended |
|---|---|---|
| Operating System | Windows 10 Build 19041 | Windows 11 22H2+ |
| Node.js | v22.19+ | v24 LTS [4] |
| RAM | 4 GB | 8 GB (16 GB for local AI models) [8] |
| Disk Space | 1 GB free | 10 GB+ [8] |
| Additional Tools | Git, WebView2 Runtime | PowerShell 7+ |
The Windows Hub companion app depends on the WebView2 Runtime. While this runtime comes pre-installed on Windows 11, Windows 10 users may need to download the Evergreen Standalone Installer from Microsoft’s website [2]. If you plan to use the WSL2 installation path, enable virtualization in your BIOS settings first [7].
OpenClaw relies on Node.js for its gateway and CLI. Here’s how to set it up:
.msi file with default settings. Check the option to “Automatically install the necessary tools” for native module support.Verify the installation by opening PowerShell and running each command separately:
node --version
npm --versionBoth commands should return version numbers. If you plan to install OpenClaw from source or a development channel, also download Git from git-scm.com using the default install options.
To install OpenClaw, open PowerShell (Administrator rights are not required for the standard install) and run:
iwr -useb https://openclaw.ai/install.ps1 | iexThis script detects your environment, installs OpenClaw globally via npm, and launches the onboarding wizard. The process typically takes around 2 minutes [4][7]. During setup you’ll configure your messaging platform, add your AI provider credentials, and start the gateway daemon. Once complete, the OpenClaw dashboard opens in your default browser on port 18789.
Confirm everything is running by checking the version and gateway status:
openclaw --version
openclaw gateway statusIf both commands return output without errors, the installation is complete.
Here are the most frequent issues and their fixes:
For any lingering issues, run the built-in diagnostic tool:
openclaw doctor --repairThis identifies and resolves common setup problems automatically.
With OpenClaw installed, the next step is choosing where to run it long-term. There are three main options, each suited to different needs and skill levels.
Running OpenClaw on your own Windows PC is the simplest starting point — no extra cost if you already have the hardware, and setup takes minutes. It’s a good fit for testing and short-term automation.
The downside is reliability. Sleep mode, power outages, and simply closing your laptop lid can interrupt the gateway at any moment. Keeping it running requires ongoing tweaks to power settings and task scheduling. There’s also a security angle: running an autonomous AI agent on the same machine you use for personal tasks increases your attack surface.
“Running an autonomous agent on the same computer where you do your banking is a risk most security researchers consider unacceptable.” — Shabnam Katoch, Growth Head, Better Claw [6]
A Linux VPS is the go-to for 24/7 uptime at a low price. Providers like Hetzner, DigitalOcean, and Contabo offer plans from $5 to $29/month. Running OpenClaw on a separate server also keeps your personal data isolated.
The trade-off: you need to be comfortable with SSH, terminal commands, and tools like Docker. It’s cost-effective, but the learning curve is real for anyone new to server management.
A Windows cloud desktop offers the best of both worlds: continuous availability and a familiar Windows interface you can manage via Remote Desktop (RDP). No Linux knowledge required — just connect and run OpenClaw exactly as you would locally, including the Windows Hub app.
For OpenClaw on flexidesktop, the minimum viable plan is Plan S ($29/month, 2 vCPU, 4 GB RAM, 60 GB SSD) for basic automations. For browser-control workflows, Plan M ($39/month, 3 vCPU, 8 GB RAM) is the recommended fit [6].
| Feature | Local Windows PC | Linux VPS | Windows Cloud Desktop |
|---|---|---|---|
| Uptime | Low (sleep/power issues) | High (always on) | High (always on) |
| Ease of Setup | Very easy (Windows Hub) | Challenging (CLI/SSH) | Easy (RDP + GUI) |
| Cost | $0 (existing hardware) | $5–$29/month | $29–$49/month |
| Security | Low (shared with personal data) | High (isolated) | High (sandboxed) |
| Maintenance | Manual | Manual (updates) | Minimal |
| Best For | Testing and development | Budget-friendly 24/7 use | User-friendly 24/7 operation |
Choosing the right environment is only half the battle. Here’s how to maintain uptime in each scenario.
The biggest threat to uptime on a local machine is Windows sleep mode. Go to Settings → System → Power & Sleep and set both the screen and sleep timers to Never.
For protection against power outages, a UPS (Uninterruptible Power Supply) provides enough backup power to survive brief outages or perform a safe shutdown during longer ones [5]. Abrupt shutdowns can corrupt the gateway’s state.
To run OpenClaw as a persistent background service, use PM2 or NSSM (Non-Sucking Service Manager). PM2 setup:
npm install -g pm2pm2 start "openclaw gateway start" --name openclawpm2 saveThis ensures the gateway restarts automatically if it crashes [3].
For smoother performance, add the npm cache folder (%AppData%\npm) and node.exe to Windows Defender‘s exclusion list to reduce scan overhead [7][9].
On Linux, register OpenClaw as a systemd user service to start it automatically at boot and restart it after crashes. To keep it running after you log out, enable lingering for your user:
sudo loginctl enable-linger "$(whoami)"“WSL2 remains the most Linux-compatible Gateway runtime on Windows… every feature the docs describe works exactly as written.” — OpenClaw Documentation [1]
If you’re using WSL2 on a VPS, the same linger command applies. Also ensure port 18789 is open in your cloud provider’s firewall so the gateway remains accessible.
A Windows cloud desktop stays online regardless of your local internet or power situation. Register the gateway as a Windows Scheduled Task so it starts automatically on boot:
openclaw gateway installYou can then manage everything remotely via RDP while OpenClaw runs in the background [1][7].
For added crash recovery, combine the Scheduled Task with PM2 [3]. Also set the Windows power plan to High Performance and disable sleep and hibernation to prevent default settings from disrupting the gateway.
On flexidesktop for automation and bots, the Plan S ($29/month, 2 vCPU, 4 GB RAM) handles basic automation, while Plan M ($39/month, 3 vCPU, 8 GB RAM) is better suited for heavier browser-automation workflows.
“Cron jobs are worthless if the process dies every time you close your laptop lid.” — Sawyer Ruhl, ComputerTech [3]
If you run into problems, use the diagnostic tool:
openclaw doctorIt checks for Node.js version mismatches, API key errors, network connectivity issues, and daemon status — resolving most Windows-specific concerns before you need to dig deeper [8].
The right deployment depends on your technical comfort, budget, and uptime requirements.
| Your Situation | Best Option |
|---|---|
| Casual testing or non-critical tasks | Local Windows PC |
| Comfortable with Linux and on a budget | Linux VPS ($5–$29/month) |
| Need 24/7 uptime with a familiar Windows interface | Windows Cloud Desktop ($29–$39/month) |
| Prefer strong security with minimal setup | Windows Cloud Desktop |
For most non-technical users who want OpenClaw running around the clock without managing a Linux server, a Windows cloud desktop is the practical choice. It stays online continuously, connects through a familiar desktop interface, and eliminates the hardware variables that make local setups unreliable.
Run OpenClaw 24/7 on a Windows Cloud Desktop.
Plan S from $29/month, Plan M from $39/month. No Linux required — connect via RDP and run OpenClaw just like on your own PC.
Israel de la Torre is the founder of flexidesktop and has spent 15+ years working in cloud infrastructure and Windows virtualization. He helps businesses migrate from on-premises Windows setups to managed cloud desktops.
Avoid missed deadlines and lost clients with a cloud PC—access your desktop and files from any device with daily backups.
Cloud Windows desktops beat local and VPS setups for reliable, GUI-based 24/7 automation.
Local virtualization or cloud desktops — weigh performance, cost, and convenience when running Windows apps on a Mac.
Guide for law firms choosing secure Windows cloud desktops: prioritize security, Windows app compatibility, uptime, and transparent pricing.
Compare costs, deployment, security, and the best hosted Windows desktop options for small businesses.
Likely in late 2026–2027, the next Windows may add AI agents, cloud desktops and NPU support; use cloud desktops to try features.
DRAM and NAND costs surged as manufacturers focus on AI HBM, driving cloud price increases; strategies to lock pricing, right‑size resources, and cut costs.
Cloud PCs: cloud-hosted Windows desktops with centralized management and predictable monthly costs — best with reliable internet; not for hardware-heavy or offline work.
Compare Windows 365, Azure Virtual Desktop, and flexidesktop by cost, setup time, and management to find the right cloud desktop for your team’s size and skills.
