Update Node.js requirement and Pi packages
TL;DR
Raised the minimum supported Node.js version to 22.19 and updated Pi packages to version 0.75.1 to ensure compatibility with the latest runtime features.
## What changed OpenClaw raised the minimum supported Node.js version to 22.19. The project also updated its Pi packages to version 0.75.1.
These shifts target compatibility with newer runtime features in the current Node release. The change appears in the latest self-hosted build notes dated around mid-May 2026.
## Why it matters Self-hosted users must now run a more recent Node environment or face install failures. This move reduces drift from upstream changes but increases the setup burden for anyone on pinned LTS versions.
The bet is that tighter runtime alignment will cut downstream bugs in browser control and shell tasks. It pressures casual Vibe Builders who treat the agent as set-and-forget infrastructure.
## How to use it Run node -v on your VPS or WSL instance. Upgrade to 22.19 or higher through nvm or the official binaries before reinstalling OpenClaw.
After the Node update, pull the fresh Pi packages at 0.75.1 via the existing CLI install command or npm update inside the project directory. Test a heartbeat check-in and one browser task to confirm stability.
## Watch for Fewer runtime errors on fresh installs would support the change. Widespread reports of broken shell scripts or MCP bridges would signal the update moved too fast. Expect the team to drop support for Node 20 entirely in the next quarter.
Harsh’s take
A solo Vibe Builder now carries an extra maintenance task: keeping Node current on the VPS that runs the agent. The trade-off is fewer obscure compatibility crashes against more frequent environment checks that eat into the time saved by automation.
Sticking with an older Node version will simply block future OpenClaw releases. The project has already shown it will not wait for stragglers.
Update your Node install and re-test the full stack this week. Skip the update only if you are willing to fork and pin the prior version yourself.
by Harsh Desai
About OpenClaw
View the full OpenClaw page →All OpenClaw updatesMore from OpenClaw
- FeatureExpand QA-Lab with runtime parity scenarios
Added comprehensive runtime parity tiers and token-efficiency artifacts to the QA-Lab, including specific checks for Codex-vs-Pi compatibility and tool fixture coverage.
- App UpdateOptimize Gateway startup and restart latency
Reduced restart ready latency by overlapping startup logging and plugin-service initialization with channel sidecars while maintaining strict readiness gating.
- IntegrationSupport HTTPS managed forward-proxy endpoints
The proxy system now supports HTTPS managed forward-proxy endpoints and introduces `proxy.tls.caFile` for configuring scoped CA trust for proxy TLS connections.