ContextQMD
Back to Openclaw

Node.js

docs/install/node.md

2026.7.13.6 KB
Original Source

OpenClaw requires Node 22.22.3+, Node 24.15+, or Node 25.9+. Node 24 is the default and recommended runtime for installs, CI, and release workflows; Node 22 remains supported via the active LTS line. Node 23 is unsupported. The installer script detects and installs Node automatically — use this page when you want to set up Node yourself (versions, PATH, global installs).

Check your version

bash
node -v

v24.15.0 or newer 24.x is the recommended default. v22.22.3 or newer 22.x is the supported Node 22 LTS path; Node v25.9.0+ is also supported. Node 23 is unsupported. If Node is missing or outside the supported range, pick an install method below.

Install Node

<Tabs> <Tab title="macOS"> **Homebrew** (recommended): 
```bash
brew install node
```

Or download the macOS installer from [nodejs.org](https://nodejs.org/).
</Tab> <Tab title="Linux"> **Ubuntu / Debian:** 
```bash
curl -fsSL https://deb.nodesource.com/setup_24.x | sudo -E bash -
sudo apt-get install -y nodejs
```

**Fedora / RHEL:**

```bash
sudo dnf install nodejs
```

Or use a version manager (see below).
</Tab> <Tab title="Windows"> **winget** (recommended): 
```powershell
winget install OpenJS.NodeJS.LTS
```

**Chocolatey:**

```powershell
choco install nodejs-lts
```

Or download the Windows installer from [nodejs.org](https://nodejs.org/).
</Tab> </Tabs> <Accordion title="Using a version manager (nvm, fnm, mise, asdf)"> Version managers let you switch between Node versions easily. Popular options:
  • fnm - fast, cross-platform
  • nvm - widely used on macOS/Linux
  • mise - polyglot (Node, Python, Ruby, etc.)

Example with fnm:

bash
fnm install 24
fnm use 24
<Warning> Initialize your version manager in your shell startup file (`~/.zshrc` or `~/.bashrc`). If you skip this, `openclaw` may not be found in new terminal sessions because PATH won't include Node's bin directory. </Warning> </Accordion>

Troubleshooting

openclaw: command not found

This almost always means npm's global bin directory isn't on your PATH.

<Steps> <Step title="Find your global npm prefix"> ```bash npm prefix -g ``` </Step> <Step title="Check if it's on your PATH"> ```bash echo "$PATH" ``` 
Look for `<npm-prefix>/bin` (macOS/Linux) or `<npm-prefix>` (Windows) in the output.
</Step> <Step title="Add it to your shell startup file"> <Tabs> <Tab title="macOS / Linux"> Add to `~/.zshrc` or `~/.bashrc`: 
    ```bash
    export PATH="$(npm prefix -g)/bin:$PATH"
    ```

    Then open a new terminal (or run `rehash` in zsh / `hash -r` in bash).
  </Tab>
  <Tab title="Windows">
    Add the output of `npm prefix -g` to your system PATH via Settings → System → Environment Variables.
  </Tab>
</Tabs>
</Step> </Steps>

Permission errors on npm install -g (Linux)

If you see EACCES errors, switch npm's global prefix to a user-writable directory:

bash
mkdir -p "$HOME/.npm-global"
npm config set prefix "$HOME/.npm-global"
export PATH="$HOME/.npm-global/bin:$PATH"

Add the export PATH=... line to your ~/.bashrc or ~/.zshrc to make it permanent.