Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug] Companion v2026.10.5-alpha.4 WSL setup fails: pinned Node 24.19.0 rejected by install-cli (requires 24.22.1+)

Open Beginner friendly
  • Is something wrong?
#1,843 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp, node.js
Domain
backend, devtools

Research direction

Read src/OpenClaw.SetupEngine/GatewayInstallPolicy.cs and compare the Node version pinned in the released tag with the current main value mentioned in the issue. Check the setup engine's CLI installation path and relevant tests. Done means the installer selects a Node version accepted by the OpenClaw CLI and the local WSL Gateway setup passes install-cli.

Written by the indexing model from the issue text.

Description

clawsweeper:fix-shape-clear clawsweeper:needs-maintainer-review clawsweeper:no-new-fix-pr clawsweeper:not-repro-on-main impact:ux-release-blocker issue-rating: 🦪 silver shellfish P0

Summary

A clean local WSL Gateway setup through OpenClaw Companion v2026.10.5-alpha.4 (Windows x64) fails at install-cli because the setup engine pins Node.js 24.19.0, but the current OpenClaw CLI installer requires Node.js 24.22.1+ or 26.12.1+.

This blocks onboarding even though the Windows/WSL preflight steps succeed.

Environment

  • OpenClaw Companion: v2026.10.5-alpha.4 (Windows x64 installer)
  • OS: Windows 11 x64, build 26200.6584 (reported by WSL)
  • Installation path: Install a local Gateway (WSL)
  • WSL distro: Ubuntu 24.04 as app-owned OpenClawGateway
  • Permissions preset: Strict

Actual behavior

The setup progresses through WSL compatibility checks and Gateway preparation, then fails at the CLI installation step:

Step 'install-cli' failed: CLI install failed (exit 1):
ERROR: Node 24.19.0 is unsupported; use Node 24.22.1+ or Node 26.12.1+.

The preceding log confirmed the installer invoked wsl.exe --install --distribution Ubuntu-24.04 --name OpenClawGateway ... --no-launch --web-download, and this subsequent failure occurs at install-cli. An earlier attempt had failed during wsl-create with exit -1 and no output, but the latest attempt progressed beyond WSL creation.

Source evidence

The released tag pins an incompatible version in src/OpenClaw.SetupEngine/GatewayInstallPolicy.cs:

This appears to be a release/source version drift rather than missing WSL support or a user-provided Node installation problem.

Related older reports with the same failure pattern for a previous pinned Node version: #1364 and #1394.

Expected behavior

The graphical Windows Companion setup should select a Node.js version accepted by the OpenClaw CLI installer and complete local Gateway setup without requiring users to manually modify WSL or install another runtime.

Request

Could you publish a refreshed Windows x64 Companion installer incorporating the corrected Node pin, or provide an official GUI-supported recovery/update path for installations already blocked at install-cli?

No security controls or WSL isolation settings were disabled during these attempts.

Dominant language
C#
Stars
2.2k
Forks
321
Avg merge
4d 14h
Merged PRs (30d)
187

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openclaw/openclaw-windows-node

All issues in openclaw/openclaw-windows-node

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.