OpenClaw: Installer Failed

The installer performs several phases: environment detection, Node setup when needed, the OpenClaw package installation, and onboarding. Identify which phase failed before rerunning it.

Preserve the useful error

Keep the command output, operating system, shell, and exact first error. Remove tokens or private paths before sharing a log. Do not paste a credential returned during onboarding into an issue.

Check the basic dependencies

node --version
npm --version
curl --version

On PowerShell, confirm that script execution, TLS, and network policy permit the official installer URL. On macOS or Linux, distinguish a download failure from a package-install failure.

Follow the matching branch

• Unsupported Node: use the Node version fix.
• EACCES or operation not permitted: use the permission fix.
• npm registry, certificate, or package error: use the npm install guide.
• CLI installed but not found: repair PATH with the command-not-found guide.

Retry once

After fixing the first failure, rerun the official command from the install guide. If onboarding is the only failing stage, install with --no-onboard, verify the CLI, and run openclaw onboard separately.

Expected result

The installer reaches a successful package install, openclaw --version works in a fresh shell, and onboarding or openclaw doctor can run independently.