How to Install OpenClaw in 2026

Install time is usually 2 to 5 minutes. Onboarding typically takes 5 to 15 minutes, depending on whether you use the installer script or the npm path.

Prerequisites

Before you start, make sure you have a supported Node version. The docs recommend Node 24, and Node 22.16+ is still supported.

Want a dedicated always-on host? The Apple Mac mini M4 (16GB) is the most popular choice for running OpenClaw 24/7. See our Mac mini setup guide.

• macOS: supported.
• Linux: supported.
• Windows: supported, with WSL2 strongly recommended.

If you are on macOS or Linux and install with npm, the docs call out this PATH fix:

export PATH="$(npm prefix -g)/bin:$PATH"

Fastest Install Path

The fastest official route is the installer script:

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

The FAQ also shows this as the recommended pair when you want the full guided setup:

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

If you want to skip onboarding for now, use:

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

After the install finishes, the docs recommend continuing with onboarding so OpenClaw can finish setting up your local environment.

npm Install Path

If you prefer npm, the official path is:

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

That path is useful if you want a more explicit CLI workflow or you are already managing global Node tools this way.

What Onboarding Does

The CLI onboarding step is:

openclaw onboard

Use it when you want OpenClaw to walk through the first-run setup rather than stopping after the binary is installed. If you skipped onboarding during install, run it afterward.

First Successful Chat

Once onboarding is complete, the fastest way to test the install is:

openclaw dashboard

That is the quickest way to confirm the install is live and ready for a first conversation.

Common Install Gotchas

• If a global npm install does not resolve correctly, check the PATH fix above.
• If you are on Windows, use WSL2 unless you have a specific reason not to.
• If install or onboarding fails after the binary is present, start with the troubleshooting guide below.
• If you skipped onboarding with --no-onboard, run openclaw onboard afterward.

For the most common setup errors after install, see the OpenClaw troubleshooting guide. It covers token issues, Docker config problems, blank responses, Windows PATH issues, macOS gateway persistence, and port conflicts.

If you are installing on a dedicated Apple machine, see OpenClaw on Mac Mini. If you want a Qwen-backed setup, see OpenClaw + Qwen.