The Operator Vault Install Guide

How to Install OpenClaw:
Step-by-Step Guide

One command. Five minutes. Your agent is live.

We've installed OpenClaw on every platform. Here's the fastest path on each one. No containers required, no complex dependencies. Just Node.js 22 and one line in your terminal.

>_Start the $19 Workshop

Choose your platform

Install in one command.

Prerequisites

node --version  # Must be v22+

Install

$ curl -fsSL https://openclaw.ai/install.sh | bash

Installs OpenClaw globally via npm. Requires Node.js 22 or newer.

After installation

The onboarding wizard.

After the install script finishes, run the onboarding wizard. In our experience, this is where most people either get it right in five minutes or spend an hour confused. Here is what to expect at each step.

$ openclaw onboard --install-daemon
1

Provider Authentication

The wizard asks which AI model provider you want to use. Anthropic, OpenAI, Google, or a custom provider. Paste your API key or use OAuth for subscription-based access.

We recommend Anthropic API keys for the simplest setup. Create one at console.anthropic.com.

2

Gateway Configuration

Choose whether to run the Gateway locally (recommended for testing) or bind it to a network interface for remote access. The wizard auto-generates a secure gateway token.

Local mode binds to 127.0.0.1:18789 by default. Safe for first-time setup.

3

Daemon Installation

Use the --install-daemon flag to register OpenClaw as a system service. On macOS it creates a launchd plist. On Linux it creates a systemd unit. The gateway will start automatically on boot.

Run: openclaw onboard --install-daemon

4

Channel Setup (Optional)

Connect WhatsApp, Telegram, Discord, or other messaging channels. You can skip this step and use the built-in WebChat UI instead. Channels can be added later at any time.

You do not need channels to start using OpenClaw. The Control UI works immediately.

Zero channel setup required

Your first conversation.

You do not need to configure WhatsApp, Telegram, or any channel to start. OpenClaw ships with a browser-based Control UI that works the moment the Gateway starts.

Check the Gateway
$ openclaw gateway status
Open the Control UI
$ openclaw dashboard
Or open it directly
# Visit http://127.0.0.1:18789/ in your browser

No channel setup needed. If the Control UI loads, your Gateway is healthy and ready. You can type messages directly in the browser. Add WhatsApp, Telegram, or Discord channels later when you are ready.

Setting up channels can take a full afternoon if you're starting from scratch. The $19 workshop covers WhatsApp, Telegram, and Discord setup in under 15 minutes. Learn more

Reference

Environment variables.

Here are the environment variables you'll encounter during setup, with our recommendations for each. Most users never need to touch them, but they are here when you do.

OPENCLAW_HOME~

Sets the home directory for internal path resolution. All state and config paths derive from this.

OPENCLAW_STATE_DIR~/.openclaw

Override the directory where OpenClaw stores config, credentials, sessions, and agent state.

OPENCLAW_CONFIG_PATH~/.openclaw/openclaw.json

Override the config file path. Useful when running multiple Gateway profiles.

OPENCLAW_PROFILEdefault

When set to a non-default value, workspace becomes ~/.openclaw/workspace-<profile>. Useful for parallel setups.

OPENCLAW_GATEWAY_TOKEN(auto-generated)

Authentication token for WebSocket connections. Required when the Gateway binds to non-loopback addresses.

OPENCLAW_GIT_DIR~/openclaw

Override the git checkout directory when using the dev update channel.

Configuration mistakes are the #1 reason people get stuck. The workshop walks you through every file in the workspace. Start the $19 workshop

If something breaks

Troubleshooting.

We've walked hundreds of people through OpenClaw installation. Here are the errors that come up most often, and the fixes we've discovered along the way.

Error
Error: Node.js version must be >= 22

Update Node.js to version 22 or newer. Use nvm: "nvm install 22 && nvm use 22" or download directly from nodejs.org.

Error
EACCES: permission denied, mkdir '/usr/local/lib/node_modules'

Fix npm permissions: "sudo chown -R $(whoami) /usr/local/lib/node_modules" or use nvm which avoids global permission issues entirely.

Error
openclaw: command not found

The npm global bin directory is not in your PATH. Run: npm config get prefix, then add the bin/ directory to your shell profile.

Error
Error: Cannot find module 'openclaw'

The install may have failed silently. Run "npm install -g openclaw@latest" manually and check for error output.

Error
ECONNREFUSED 127.0.0.1:18789

The Gateway is not running. Start it with "openclaw gateway" in the foreground, or check the service status with "openclaw gateway status".

Error
Docker: permission denied while trying to connect to the Docker daemon

Add your user to the docker group: "sudo usermod -aG docker $USER" then log out and back in. On macOS, ensure Docker Desktop is running.

Stay current

Update channels.

Recommended

stable

npm tag: latest

Vetted builds promoted from beta. Recommended for production use and personal assistants.

openclaw update --channel stable

beta

npm tag: beta

Builds under active testing. May include unreleased features. Good for early adopters who want to try new capabilities.

openclaw update --channel beta

dev

npm tag: dev

Tracks the main branch head. Switches to a git checkout. Only for contributors and developers.

openclaw update --channel dev

Installed? Great.

What comes next.

A local install is perfect for learning. For a production assistant that stays online 24/7, we recommend a VPS. Your laptop sleeps. A server does not. Here are the guides we suggest reading next.

Configure your workspace filesLearn about AGENTS.md, SOUL.md, channels, and the workspace file map.
Deploy to a Cloud VPSMove OpenClaw to a VPS for 24/7 uptime, persistent channels, and background heartbeats.
Run with DockerContainerized gateway for isolated, reproducible deployments.
Read the security guideFirewall rules, sandboxing, allowlists, and access control for production.
Kevin Jeppesen, Founder of The Operator Vault

Written by

Kevin Jeppesen

Founder, The Operator Vault

Kevin is an early OpenClaw adopter who has saved an estimated 400 to 500 hours through AI automation. He stress-tests new workflows daily, sharing what actually works through step-by-step guides and a security-conscious approach to operating AI with real tools.

Install FAQ

Questions about installation.

Skip the guesswork.
Get running in 20 minutes.

The $19 workshop walks you through install, security, first run, your first workflow, and connecting channels. Step by step, with real commands.

>_Start the $19 WorkshopDone-For-You Setup