If install succeeds but `openclaw` is not found in a new terminal, see [Node.js troubleshooting](/install/node#troubleshooting).
install.sh
Recommended for most interactive installs on macOS/Linux/WSL.
Flow (install.sh)
Supports macOS and Linux (including WSL). If macOS is detected, installs Homebrew if missing.
Checks Node version and installs Node 24 if needed (Homebrew on macOS, NodeSource setup scripts on Linux apt/dnf/yum). OpenClaw still supports Node 22 LTS, currently `22.14+`, for compatibility.
Installs Git if missing.
- `npm` method (default): global npm install
- `git` method: clone/update repo, install deps with pnpm, build, then install wrapper at `~/.local/bin/openclaw`
- Refreshes a loaded gateway service best-effort (`openclaw gateway install --force`, then restart)
- Runs `openclaw doctor --non-interactive` on upgrades and git installs (best effort)
- Attempts onboarding when appropriate (TTY available, onboarding not disabled, and bootstrap/config checks pass)
- Defaults `SHARP_IGNORE_GLOBAL_LIBVIPS=1`
Source checkout detection
If run inside an OpenClaw checkout (package.json + pnpm-workspace.yaml), the script offers:
use checkout (git), or
use global install (npm)
If no TTY is available and no install method is set, it defaults to npm and warns.
The script exits with code 2 for invalid method selection or invalid --install-method values.
Designed for environments where you want everything under a local prefix
(default `~/.openclaw`) and no system Node dependency. Supports npm installs
by default, plus git-checkout installs under the same prefix flow.
Flow (install-cli.sh)
Downloads a pinned supported Node LTS tarball (the version is embedded in the script and updated independently) to `/tools/node-v` and verifies SHA-256.
If Git is missing, attempts install via apt/dnf/yum on Linux or Homebrew on macOS.
- `npm` method (default): installs under the prefix with npm, then writes wrapper to `/bin/openclaw`
- `git` method: clones/updates a checkout (default `~/openclaw`) and still writes the wrapper to `/bin/openclaw`
If a gateway service is already loaded from that same prefix, the script runs
`openclaw gateway install --force`, then `openclaw gateway restart`, and
probes gateway health best-effort.
On Linux, force npm prefix to ~/.npm-global if current prefix is not writable
--help
Show usage (-h)
Variable
Description
OPENCLAW_PREFIX=<path>
Install prefix
OPENCLAW_INSTALL_METHOD=git|npm
Install method
OPENCLAW_VERSION=<ver>
OpenClaw version or dist-tag
OPENCLAW_NODE_VERSION=<ver>
Node version
OPENCLAW_GIT_DIR=<path>
Git checkout directory for git installs
OPENCLAW_GIT_UPDATE=0|1
Toggle git updates for existing checkouts
OPENCLAW_NO_ONBOARD=1
Skip onboarding
OPENCLAW_NPM_LOGLEVEL=error|warn|notice
npm log level
SHARP_IGNORE_GLOBAL_LIBVIPS=0|1
Control sharp/libvips behavior (default: 1)
install.ps1
Flow (install.ps1)
Requires PowerShell 5+.
If missing, attempts install via winget, then Chocolatey, then Scoop. Node 22 LTS, currently `22.14+`, remains supported for compatibility.
- `npm` method (default): global npm install using selected `-Tag`
- `git` method: clone/update repo, install/build with pnpm, and install wrapper at `%USERPROFILE%\.local\bin\openclaw.cmd`
- Adds needed bin directory to user PATH when possible
- Refreshes a loaded gateway service best-effort (`openclaw gateway install --force`, then restart)
- Runs `openclaw doctor --non-interactive` on upgrades and git installs (best effort)
Git is required for `git` install method. For `npm` installs, Git is still checked/installed to avoid `spawn git ENOENT` failures when dependencies use git URLs.
Some Linux setups point npm global prefix to root-owned paths. `install.sh` can switch prefix to `~/.npm-global` and append PATH exports to shell rc files (when those files exist).
The scripts default `SHARP_IGNORE_GLOBAL_LIBVIPS=1` to avoid sharp building against system libvips. To override:
Install Git for Windows, reopen PowerShell, rerun installer.
Run `npm config get prefix` and add that directory to your user PATH (no `\bin` suffix needed on Windows), then reopen PowerShell.
`install.ps1` does not currently expose a `-Verbose` switch.
Use PowerShell tracing for script-level diagnostics: