OPENCLAW ACADEMYLEARN / FIELD MANUAL
Lesson 2 of 6 · 0%Install deliberately on macOS, Linux, Windows, WSL, or a VPSNext
Course map

Safe Installation and First Agent

0 of 6 complete0 of 6

Lesson 2.1 · 35 minutes

Install deliberately on macOS, Linux, Windows, WSL, or a VPS

Use the supported platform installer path, preserve a version record, and avoid privileged or opaque shortcuts.

Skip course map
Current lessonInstall deliberately on macOS, Linux, Windows, WSL, or a VPS0% complete · 0/6 lessons

Safe Installation and First Agent

0% complete · Current: Install deliberately on macOS, Linux, Windows, WSL, or a VPS

Verifiedon 2026.7.1-2

Action boundary

Before you act

Expected result
The OpenClaw CLI is available to the intended non-production user and its version is recorded.
Failure mode
A global install uses an unknown privilege boundary, unsupported Node runtime, or shell path that the intended user cannot execute.
Rollback
Use the official uninstall guidance for the selected path; remove only the dedicated test installation after preserving redacted evidence.

Use the supported path for your platform

The primary installer documentation distinguishes macOS/Linux/WSL from Windows PowerShell. It states support for Node 22.22.3+, 24.15+, or 25.9+. Do not “fix” an unsupported runtime by using sudo or by pasting a package command from an unreviewed video.

  • macOS/Linux/WSL2: use the documented installer or the documented package-manager route under the intended local user. The installer can provision a supported Node runtime when needed.
  • Windows: use the documented PowerShell installer or supported Windows desktop path. If Windows reports that openclaw is not recognized, check the user-level npm prefix and reopen PowerShell; do not blindly alter machine-wide PATH.
  • VPS: create and use a dedicated non-root service account, decide how you administer it before installation, and keep the state/workspace backup plan outside the VPS.

Lab: install with a record

Read the official install page for your exact path immediately before running it. Record the page URL, upstream revision, date, and the command you chose in a private local evidence file. Then confirm the command is intended for the current user and the test workspace. To keep installation separate from provider setup, use the documented no-onboarding form for your platform:

curl -fsSL https://openclaw.ai/install.sh | bash -s -- --no-onboard
& ([scriptblock]::Create((iwr -useb https://openclaw.ai/install.ps1))) -NoOnboard

Inspect the fetched script when your policy requires it; stop if the URL, signature policy, or requested privilege differs from your pre-flight record. Run only the command for your platform.

Check: prove the binary, not the demo

Run openclaw --version. Record only the version string and platform. If the binary is missing, stop and follow the documentation’s platform-specific PATH troubleshooting. If the version is not in your intended range, remove the test installation rather than continuing.

Common failure patterns

  • EACCES on Linux: a root-owned global npm prefix is likely involved. Use the documented user-prefix remediation, not a persistent root install.
  • openclaw unavailable after installation: a shell PATH refresh or incorrect npm prefix is more likely than a failed install.
  • Windows Git/Node error: restore the documented prerequisite, reopen the shell, and rerun only the installer step.
Source provenanceVerification and sources

Review receipt rr_setup_install

Outcome
approved
Method
source-review
Reviewer
forge-independent-review
Reviewed

Evidence

Limitations

  • Independent source review approved the bounded procedure; no software was installed on a learner host.

Open the public evidence snapshot

Lesson checkpoint

Ready to move on?

Mark this lesson complete when you can apply its outcome without relying on the examples above.

Next: Onboard a provider without leaking its credential