Before installing OpenClaw, decide whether you want a normal desktop experience, a local command-line Gateway, a reproducible server deployment, or a source-development environment. The methods can run the same core product, but their update channels, Node.js ownership, permission boundaries, and troubleshooting paths differ.

The commands below were checked against official documentation on September 1, 2026. Installers, minimum versions, and download assets change. Confirm that you are using openclaw.ai, docs.openclaw.ai, or the official GitHub organization before execution.

OpenClaw system requirements

OpenClaw currently supports macOS, Linux, and Windows. Windows users may choose Windows Hub, the PowerShell installer, or a WSL2 Gateway. Command-line installations need a supported Node.js release: Node 22.22.3+, 24.15+, or 25.9+ (including Node 26). The current recommendation is Node 26.

Inspect the existing environment with:

node -v
uname -a

On Windows, use node -v in PowerShell and check system settings for the processor architecture. pnpm is required only when building from source; the normal official installer handles the primary dependencies.

Option one: download a desktop app

Users who do not want to manage a terminal and Node.js first can follow the official downloads linked from the OpenClaw overview. Windows Hub includes setup, tray status, chat, and node mode. The macOS app is distributed as a .dmg or .zip asset.

During the first run, a desktop app can provision a local Gateway or connect to an existing remote Gateway. Check the publisher and code signature. Avoid repackaged “localized” installers, file-sharing mirrors, and unofficial cracked applications.

Option two: use the official installer

This is the recommended command-line path. On macOS, Linux, or WSL2, run:

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

On Windows PowerShell, run:

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

The installer detects the platform, provisions a supported Node.js release when needed, installs OpenClaw, and launches onboarding. In a higher-security environment, download and review the script before running it in a test account. Reviewing a script means more than checking its filename.

Option three: install with npm or pnpm

Developers who already manage Node.js can install the package globally. Current official guidance for npm 12 or npm 11.16+ explicitly permits OpenClaw lifecycle scripts:

npm install -g openclaw@latest --allow-scripts=openclaw
openclaw onboard --install-daemon

With pnpm, approve the required build script explicitly:

pnpm add -g --allow-build=openclaw openclaw@latest
openclaw onboard --install-daemon

Do not make sudo npm install -g the permanent answer to permission failures. Prefer a version manager or user-writable global prefix, and continue with the OpenClaw Node.js environment guide.

Choosing containers, source, or a local prefix

For servers and isolated deployments, evaluate the official Docker, Podman, Nix, Ansible, or hosting instructions. Containers do not solve credential storage, persistence, or network exposure automatically. Plan state volumes, backups, Gateway authentication, and updates.

Contributors can clone the official GitHub repository and build with the pnpm version pinned by the project. Ordinary users should not treat main as a stable release. To avoid a system-level Node and global package directory, the official install-cli.sh keeps Node and OpenClaw under a local ~/.openclaw prefix.

How to verify an OpenClaw installation

After any installation method, run:

openclaw --version
openclaw doctor
openclaw gateway status

The version command confirms that the CLI resolves, doctor checks dependencies and configuration, and Gateway status checks the background service. Open the Control UI, complete one low-risk conversation, and confirm that tool calls require the intended approvals.

If the shell reports openclaw: command not found, the global bin directory is usually absent from PATH. Run npm prefix -g, then add the relevant path through the active shell or Windows environment settings. Installing several copies hides the PATH problem instead of fixing it.

  • Typical macOS or Windows user: official desktop app.
  • Developer running a local Gateway: official installer script.
  • Team with established Node.js management: npm or pnpm with a defined channel.
  • Server or reproducible deployment: official container or platform guide with persistence and authentication.
  • OpenClaw contributor: source build in an isolated development environment.

Whichever method you choose, record the source, version channel, configuration location, and removal procedure. A maintainable installation is not merely a successful command; it is an environment you can explain during the next update or failure.

Published
Information verified
By
AI Tool Blog Editorial Team