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.
Who this matters for
- Vibe Builders: Update your VPS to Node.js 22.19 immediately to prevent OpenClaw installation and runtime failures.
- Developers: Align your local dev environment with Node 22.19 to utilize the latest runtime features in OpenClaw.
Harsh’s take
This update forces a hard pivot to Node.js 22.19, signaling that OpenClaw is prioritizing modern runtime features over legacy stability. For operators, this means the era of set and forget infrastructure for this agent is over. You must actively manage your versioning via nvm or risk broken shell tasks and MCP bridges.
The move to Pi packages 0.75.1 alongside the Node bump suggests a tighter integration between the agent logic and the underlying system environment. While this reduces technical debt and drift from upstream changes, it increases the maintenance overhead for self-hosted deployments. If you are running OpenClaw on a pinned LTS version, your stack is now officially deprecated.
Move to the latest stable release now or expect your automation scripts to fail during the next package pull.
by Harsh Desai
About OpenClaw
View the full OpenClaw page →All OpenClaw updatesGo deeper
More AI news
- FeatureHermes Agent verifies work with completion contracts and evidence ledgers
Hermes Agent records verification evidence for coding tasks. The /goal command uses completion contracts to judge success against test runs rather than model assertions.
- FeatureCursor adds cloud agent management to the Agents window
Cursor sets up cloud development environments in under 10 minutes, spins up isolated cloud subagents using /in-cloud, and hands off sessions between local and cloud.
- FeatureCursor introduces /automate skill for automating repetitive tasks
Cursor's new /automate skill creates automations from plain language. Workflows trigger via Slack emojis or GitHub events while cloud agents access virtual computers.