OpenClaw install fails: "this OpenClaw release requires Node >=24.22.1 <25 || >=26.12.1"
[openclaw] error: this OpenClaw release requires Node >=24.22.1 <25 || >=26.12.1.Also appears as (2)
npm error [openclaw] detected Node 20.19.2 (exec: /usr/bin/node).Windows Companion: Node 24.19.0 is unsupported (even though Windows has Node 26 installed)
We reproduced the error and confirmed the fix on our own test machine on the date shown. Nightly CI re-runs are not running yet. How we verify.
- Last verified
- Re-test due
- Published
- Fix ID
AGT-01
Environment and versions
| os | Debian 13 (x64 container) |
|---|---|
| node before | 20.19.2 |
| node after | 26.12.1 |
| npm | 11.20.0 (bundled with Node 26.12.1) |
| openclaw | 2026.10.7 (157d8c2) |
In brief
Your Node version is older than OpenClaw's supported range. The full fix shows the supported versions, three ways to switch Node safely, the reinstall, and the check that confirms it worked, plus the Windows Companion variant.
Symptom
You run npm install -g openclaw on a VPS, a Raspberry Pi, or a laptop with an older Node, often the one your Linux distro or VPS image ships. The install stops with:
npm error [openclaw] error: this OpenClaw release requires Node >=24.22.1 <25 || >=26.12.1.
npm error [openclaw] detected Node 20.19.2 (exec: /usr/bin/node).
npm error [openclaw] install Node: https://nodejs.org/en/download
Why it happens
- Current OpenClaw only supports Node 24.22.1+ (24.x) or Node 26.12.1+. OpenClaw's Node page says Node 22, 23 and 25 are unsupported.
- The install script checks your Node version first and refuses to continue.
- Heads-up, the docs disagree with each other: on Oct 26 the "System requirements" box on docs.openclaw.ai/install still said "Node 24.16+ or 26.1+". The npm
enginesfield (>=24.22.1 <25 || >=26.12.1) is the one the installer enforces.
What we could not test
- macOS, Windows/WSL (including the Companion variant above), Raspberry Pi (ARM), and Alpine/musl.
- nvm, fnm or NodeSource specifically, and OpenClaw's own installer script.
- Starting the gateway or chatting with a model (needs a model key we don't have).
The full fix
$4The free part of this page tells you what's wrong. The full fix tells you exactly what to do. It includes:
- Step-by-step fix, safest option first (the full page is 571 words)
- 1 copy-paste block of commands, config or code
- How to check it worked
- Our test record from Oct 26, 2026: what we ran and what happened
Launching soon. Checkout isn't open yet; prices may change at launch. Join the waitlist. You can check what you'll get: SHA-256 of the full fix 4ef3dc3e00f906c2… (how to check).
Sources
- OpenClaw docs: Node.js runtime (supported versions)
- OpenClaw docs: Node.js compatibility
- OpenClaw Community forum: Installation Error - Node Version Fix (Windows Companion variant, Oct 25, 2026)
- openclaw-windows-node#1843 (Companion installs Node 24.19.0 in WSL)
- GitHub #145658: Setup fails in install-cli step due to unsupported Node version
- GitHub #164396: clean Node 22 LTS install fails to connect
- GitHub PR #81264: installer Node floor aligned with package engine
How this page was made
Drafted by an AI agent and reproduced on our test machine on Oct 26, 2026. The scripts and logs are in the repro bundle; their file hashes are public on the repro page. Human review: not yet. No warranty: try fixes on a copy or staging environment first. Machine-readable versions: Markdown · JSON.
Found a mistake or a newer version where this breaks? Tell us.