Skip to main content

​
System requirements

  • Node 22.19+, 23.11+, or 24+ - Node 24 is the default target; the installer script handles this automatically.
  • macOS, Linux, or Windows - Windows users can start with the native Windows Hub app, the PowerShell CLI installer, or a WSL2 Gateway. See Windows.
  • pnpm is only needed if you build from source.
The fastest way to install. It detects your OS, installs Node if needed, installs OpenClaw, and launches onboarding.
Windows desktop users can also install the native Windows Hub companion app, which includes setup, tray status, chat, node mode, and local MCP mode.
curl -fsSL https://openclaw.ai/install.sh | bash
To install without running onboarding: 
curl -fsSL https://openclaw.ai/install.sh | bash -s -- --no-onboard
For all flags and CI/automation options, see Installer internals.

​
Alternative install methods

​
Local prefix installer (install-cli.sh)

Use this when you want OpenClaw and Node kept under a local prefix such as ~/.openclaw, without depending on a system-wide Node install: 
curl -fsSL https://openclaw.ai/install-cli.sh | bash
It supports npm installs by default, plus git-checkout installs under the same prefix flow. Full reference: Installer internals. Already installed? Switch between package and git installs with openclaw update --channel dev and openclaw update --channel stable. See Updating.

​
npm, pnpm, or bun

If you already manage Node yourself: 
npm install -g openclaw@latest
openclaw onboard --install-daemon
The hosted installer clears npm freshness filters such as min-release-age for the OpenClaw package install. If you install manually with npm, your own npm policy still applies.

​
From source

For contributors or anyone who wants to run from a local checkout: 
git clone https://github.com/openclaw/openclaw.git
cd openclaw
pnpm install && pnpm build && pnpm ui:build
pnpm link --global
openclaw onboard --install-daemon
Or skip the link and use pnpm openclaw ... from inside the repo. See Setup for full development workflows.

​
Install from the GitHub main checkout

curl -fsSL --proto '=https' --tlsv1.2 https://openclaw.ai/install.sh | bash -s -- --install-method git --version main

​
Containers and package managers

Docker

Containerized or headless deployments.

Podman

Rootless container alternative to Docker.

Nix

Declarative install via Nix flake.

Ansible

Automated fleet provisioning.

Bun

CLI-only usage via the Bun runtime.

​
Verify the install

openclaw --version      # confirm the CLI is available
openclaw doctor         # check for config issues
openclaw gateway status # verify the Gateway is running
If you want managed startup after install:
  • macOS: LaunchAgent via openclaw onboard --install-daemon or openclaw gateway install
  • Linux/WSL2: systemd user service via the same commands
  • Native Windows: Scheduled Task first, with a per-user Startup-folder login item fallback if task creation is denied

​
Hosting and deployment

Deploy OpenClaw on a cloud server or VPS. See Linux server for the full provider picker (DigitalOcean, Hetzner, Hostinger, Fly.io, GCP, Azure, Railway, Northflank, Oracle Cloud, Raspberry Pi, and more), or deploy declaratively on Render.

VPS

Pick a provider.

Docker VM

Shared Docker steps.

Kubernetes

K8s deployment.

​
Update, migrate, or uninstall

Updating

Keep OpenClaw up to date.

Migrating

Move to a new machine.

Uninstall

Remove OpenClaw completely.

​
Troubleshooting: openclaw not found

Almost always a PATH issue: npm’s global bin directory isn’t on your shell’s PATH. See Node.js troubleshooting for the full fix, including the Windows path. 
node -v           # Node installed?
npm prefix -g     # Where are global packages?
echo "$PATH"      # Is the global bin dir in PATH?