The most common failure of OpenClaw installation is not that the project itself is broken, but that the environment is not right. OpenClaw's official open-source repository is https://github.com/openclaw/openclaw, and the installation documentation is https://docs.openclaw.ai/install/index. The official installation page is very straightforward: Node 24 is the recommended version, and Node 22.14+ can also be used; Windows can be installed natively, but WSL2 is officially recommended.
Let's take a look at the three easiest points to step on
The first is that the Node version is too old, and the installation script will get stuck directly; The second is that the Windows environment does not use WSL2, and the subsequent npm, permissions, and paths are prone to minor problems; The third is that the 'openclaw' command cannot be found after installation, most likely because the PATH is not properly configured, not because the program is not installed.
A more stable approach
If you are installing for the first time, give priority to using the official installation script, and don't spell the command yourself as soon as it comes up. The script will automatically detect the system, install nodes, and pull up onboarding, which can save a lot of corner pits. If you are already in the source code directory, the official path of git/install-cli is also supported, but the premise is still that the basic conditions of Node and Git are normal.
If it still reports an error, check in this order
- Run 'node -v' first to confirm if the version is sufficient.
- Windows users prefer to switch to WSL2 and reinstall it again.
- Run 'npm prefix -g' to check if the global bin directory has entered the PATH.
Many people interpret installation failure as "OpenClaw is not compatible with my computer", but in fact, it is often just a link in the installation link that is not ready. Complete the basics of Node, Git, WSL2, and PATH, and the installation success rate will be much higher.
