OpenClaw Install Guide: Verify Before You Copy

Start with the right questions

The fastest install guide is not the one with the longest command block. It is the one that helps you answer three questions before you begin:

1. What does the current official release require?
2. Is a local setup enough for my first pass?
3. How will I validate the install once it is done?

If you skip those questions, you may still end up with a running service, but not a usable workflow.

Step 1: confirm environment requirements

As of March 2026, OpenClaw requires:

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

Check your local toolchain first:

node -v
npm -v
git --version

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

Step 2: pick an install path

One-liner script (recommended for first-time setup)

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

Local vs longer-lived environment

Local setup is best when you want fast feedback, easy log access, and simple cleanup.

Cloud or server setup is best when you need continuous availability, team access, or a more durable deployment.

If you are still deciding whether OpenClaw fits your workflow, a local path is usually the shorter answer.

Step 3: initialize

After installation, run the onboarding wizard:

openclaw onboard --install-daemon

This walks you through model provider selection, API key configuration, channel setup, and permissions.

Step 4: validate more than "it starts"

A working install should prove more than process startup:

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 (default http://127.0.0.1:18789/)
• doctor passes all checks

Then run a minimal conversation test:

openclaw run --prompt "Hello"

If you get a normal response, the install is validated.

Step 5: treat install as the beginning, not the finish line

The first useful OpenClaw loop usually looks like this:

Install

The service runs.

Connect one channel

OpenClaw supports 12 channels. Use openclaw channels add to connect one you actually use.

Add a few starter skills

openclaw skills install @clawhub/web-search
openclaw skills install @clawhub/browser
openclaw skills install @clawhub/summarize

Run a real task

You have validated the workflow with actual work.

Common early mistakes

Over-designing the first environment

That increases setup time and makes debugging harder.

Declaring success before a real task works

A running process is not the same as a usable setup.

Adding too much extension surface too early

Skills and permissions can wait until the baseline is stable. Run openclaw security audit --deep before expanding.

Where to go next

• Open Start for the shortest post-install workflow
• Read Beginner skill picks before widening capability
• Official install docs → docs.openclaw.ai
• Issues → GitHub Issues