If you have been putting off the how to install OpenClaw step for a week or two, you are not alone. The instructions exist. The docs are solid. But there is a gap between “just run the install script” and actually having a working gateway that responds to your messages. This article closes that gap.
Below you will find the exact prerequisites, the full install sequence, and the specific errors that trip people up most often. Real commands, real fixes, no filler.
Why Installing OpenClaw Feels Harder Than It Should
OpenClaw is a self-hosted gateway. That word, “self-hosted,” scares off a lot of people who are not developers. It implies servers, configs, and things that can break at 3am. The reality is much more manageable than that picture suggests.
But there is a real friction point: OpenClaw runs on Node.js, and most small business owners have never touched Node. The install script handles most of it automatically. The problem is that when something goes wrong, the error messages assume you know what npm and PATH mean. Most people do not, and they give up at that exact moment.
So yes, you can install OpenClaw yourself. But the setup is not trivial if you have never used a terminal before. And there is no shame in deciding the time cost is not worth it. More on that later.
Rather Have Someone Handle This?
OpenClaw Ready sets up your AI agent from scratch. No terminal required.
What You Need Before You Start
Three things have to be in place before the install command will work.
Node 22 or newer. This is the single most common install failure. OpenClaw requires Node 22+. Check what you have:
node --versionIf the output is v18 or v20, or if the command returns “command not found,” you need to install or upgrade Node before anything else. The simplest path on macOS is Homebrew:
brew install nodeOn Linux, use your package manager or download directly from nodejs.org. The install script will attempt to handle this for you, but it does not always succeed on machines with older Node versions in the system PATH.
A Mac or Linux machine. OpenClaw runs on macOS, Linux, and Windows. Windows users are strongly advised to set up WSL2 first, which gives you a Linux environment inside Windows. The install experience on native Windows PowerShell is functional but more error-prone.
An API key. OpenClaw is the gateway, not the AI itself. You bring your own model provider key, such as an Anthropic or OpenAI key. The onboarding wizard will ask for it. Have it ready before you start.
How to Install OpenClaw Step by Step
The recommended method is one command. Run this in your terminal:
curl -fsSL https://openclaw.ai/install.sh | bashThe script detects your Node version, installs or updates it if needed, installs the OpenClaw CLI globally via npm, and then launches the onboarding wizard. For most people on a clean Mac or Linux machine, this is all you need.
If You Prefer npm Directly
If you already have Node 22+ and prefer to manage the install yourself:
npm install -g openclaw@latest
openclaw onboard --install-daemonRun onboarding immediately after. It sets up your auth, gateway settings, and optional channel connections. Skipping it leaves you with a CLI but no working gateway.
After the Command Runs
The onboarding wizard walks you through provider configuration and optional channel setup. When it finishes, verify the gateway is running:
openclaw gateway statusThen open the control dashboard:
openclaw dashboardIf the browser opens and you can type in the chat interface, the install worked. That is the end state you are aiming for.
Common Install Errors and How to Fix Each One
This section covers the four errors that actually stop people. Each one has a specific fix.
Error: “command not found: node” or Node version too old
This is the most common blocker. The install script found Node but it is below version 22, or Node is not installed at all.
Fix on macOS:
brew install node
# or to upgrade an existing install:
brew upgrade nodeAfter installing or upgrading, close and reopen your terminal so the new version is picked up, then verify:
node --versionIf you see v22 or higher, you are good. Run the install command again.
Error: “sharp: Please add node-gyp to your dependencies”
This one appears on macOS machines that have libvips installed via Homebrew. Sharp is a dependency of OpenClaw, and it conflicts with certain globally installed libraries.
The fix is one environment variable:
SHARP_IGNORE_GLOBAL_LIBVIPS=1 npm install -g openclaw@latestThat tells Sharp to use its own prebuilt binary instead of trying to compile against your system libraries. Most people never hit this, but if you do, it looks alarming and the solution is not obvious from the error message alone.
Error: EACCES permissions when using npm
If npm tries to install OpenClaw globally and throws a permissions error, it usually means your system Node install requires root to write to global package directories. The right fix is not to use sudo.
Instead, configure npm to use a directory you own. The cleanest solution is to use nvm (Node Version Manager) to manage Node, which handles permissions correctly by default. Or on macOS, switch to a Homebrew-managed Node install, which places global packages in a user-writable location.
If you are in a hurry and just want it working, this one-time config creates a local npm prefix:
mkdir ~/.npm-global
npm config set prefix '~/.npm-global'
export PATH=~/.npm-global/bin:$PATHAdd that export line to your ~/.zshrc or ~/.bashrc so it persists across sessions. Then retry the install.
Error: “openclaw: command not found” after install succeeds
The CLI installed but your shell cannot find it. This is a PATH issue. Close and reopen the terminal first. If that does not fix it, check where npm installed the binary:
npm bin -gThe output is the directory where global npm binaries live. If it is not in your PATH, add it. On macOS with Homebrew Node, it is usually /opt/homebrew/bin which is typically already in PATH. On a custom setup it might be something like ~/.npm-global/bin.
Stuck on the Install? We Can Take It From Here.
Our team handles the full OpenClaw install, config, and first automation.
After the Install: First Steps Worth Taking
Getting the CLI installed is not the same as having a working automation setup. A few things to do next.
Connect a channel. OpenClaw’s value comes from reaching it wherever you already work. Telegram and Discord are the most reliable starting points. The onboarding wizard covers this, but if you skipped channel setup, run openclaw onboard again. For the full walkthrough on connecting messaging apps, see Connect OpenClaw to Telegram, Discord and WhatsApp in 10 Minutes.
Set up a cron job. One of the first things worth automating is a scheduled task. OpenClaw cron runs on its own scheduler and does not depend on system cron. See OpenClaw Cron Jobs: Complete Guide to Scheduling and Automation for examples you can copy directly.
Read the review. If you want a realistic sense of what OpenClaw does well and where it has rough edges before investing more setup time, the OpenClaw Review 2026 is worth 10 minutes.
Checking Your Node Version on Different Systems
The version check is the same everywhere, but the fix varies by platform. On macOS with Homebrew, upgrading Node takes two commands:
brew update
brew upgrade nodeOn Ubuntu or Debian Linux:
curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -
sudo apt-get install -y nodejsOn Windows, the cleanest path is to install WSL2 first, then treat the rest of the process as a Linux install. Running OpenClaw in native Windows PowerShell works but produces more edge cases during setup.
When DIY Install Does Not Make Sense
There is a certain type of install session that turns into a four-hour debugging loop. You are not sure if the error is a Node version issue or a PATH issue or something specific to your machine setup. You fix one thing and hit a different error. Each fix requires googling a concept you have never needed before.
That is not a failure. It is a signal that the time cost of DIY does not match the value you are trying to get from the tool.
Most business owners who hire out the setup do it because they value their time at more than the cost of getting it done right. And setup errors that accumulate during a rushed install tend to surface later as weird behavior or broken automations that take longer to debug than doing it correctly from the start.
The setup problems people hit most often are covered in OpenClaw Setup Too Hard? Fix These 5 Common Problems in Minutes, if you want to work through them yourself first.
Want It Done Right the First Time?
Skip the troubleshooting and let our team handle the whole setup.
The OpenClaw install is genuinely achievable for a non-developer who is comfortable in a terminal and patient with error messages. Go in knowing that Node 22 is the baseline, the install script handles most edge cases, and the four errors above cover the situations where it does not. That is most of what you need.