OpenClaw setup: shortest install path first

Prerequisites

As of March 2026, OpenClaw requires:

• Node.js ≥ 22 (Node 24 recommended)
• Git
• Docker (optional, for containerized deployments)

Verify your toolchain first:

node -v
npm -v
git --version

If your Node version is below 22, upgrade before proceeding.

Install OpenClaw

One-liner script (recommended)

macOS / Linux:

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

Windows PowerShell:

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

NPM install

npm install -g openclaw@latest
openclaw onboard --install-daemon

Initialize

Run the onboarding wizard to configure model, API key, channel, and permissions:

openclaw onboard --install-daemon

Validate the install

openclaw --version
openclaw gateway status
openclaw dashboard
openclaw doctor

Expected results:

• --version returns the current version number
• gateway status shows the Gateway is running
• dashboard opens the management panel at http://127.0.0.1:18789/
• doctor passes all checks

Run a minimal test:

openclaw run --prompt "Hello"

Local first is still the practical default

For most first-time users, a local setup is the shortest route because it gives you:

• faster feedback
• easier log access
• simpler cleanup if something breaks

Only move to a longer-lived environment once you know the workflow is worth keeping around.

What matters after installation

A successful install is not the real milestone. What matters is whether OpenClaw can:

1. receive input
2. process something useful
3. return the result somewhere you actually read

That is why setup and channel choice are tightly connected.