# Windows (WSL2)

## Overview

The documentation recommends deploying OpenClaw on Windows through WSL2 (Ubuntu preferred) rather than natively, as this approach maintains consistent runtime behavior and improves compatibility with essential tooling and skills.

## Installation Path

Users should begin by establishing WSL2 with a single command, then follow the Linux-based Getting Started guide within the WSL environment. The process involves:

1. Cloning the repository
2. Installing dependencies via pnpm
3. Building the application
4. Running the onboarding workflow

## Gateway Setup

The Gateway service installs through several command options:

- `openclaw onboard --install-daemon`
- `openclaw gateway install`
- `openclaw configure` (selecting Gateway service when prompted)

Users can diagnose or repair installations using `openclaw doctor`.

## Network Configuration

A key technical consideration: WSL operates on its own virtual network separate from Windows. To enable other machines accessing services within WSL (like the Gateway), administrators must configure port forwarding using PowerShell commands that map Windows ports to the current WSL IP address. This requires reapplication after each WSL restart, though automated Scheduled Tasks can handle this.

## Current Limitations

A Windows companion app does not yet exist, though community contributions toward this feature are welcomed.
