[Bug]: npm install fails on Windows: [email protected] permission denied for libsignal-node #40684
Description
Bug type
Regression (worked before, now fails)
Summary
After upgrading from v2026.3.2 to latest (v2026.3.7), npm install -g openclaw@latest fails on Windows due to SSH authentication error for libsignal-node.
Steps to reproduce
1.On Windows (PowerShell), run:
npm install -g openclaw@latest
2.Error occurs:
[email protected]: Permission denied (publickey).
fatal: Could not read from remote repository.
Expected behavior
Installation should succeed without requiring SSH configuration, OR
Provide a fallback (HTTPS URL, npm package, or --no-signal flag)
Actual behavior
When running npm install -g openclaw@latest on Windows (PowerShell), the installation fails during dependency resolution with:
npm error code 128
npm error command git --no-replace-objects ls-remote ssh://[[email protected]](mailto:[email protected])/whiskeysockets/libsignal-node.git
npm error [[email protected]](mailto:[email protected]): Permission denied (publickey).
No further progress is made; the process exits with code 128. This occurs even after configuring git config url."https://github.com/".insteadOf="[email protected]:", indicating the SSH URL is hard-coded and not overridden by Git config.
OpenClaw version
2026.3.2
Operating system
Windows 11
Install method
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response