OpenClaw npm Install: One Command for Mac, Linux, and Windows

1 When to Use npm Instead of Other Methods

The npm install is ideal if you already manage Node.js for development. You can use the same Node version across projects, and updates are as simple as npm update -g openclaw. If you prefer minimal tooling, the one-line curl installer is faster—it installs Node.js for you if needed. Homebrew users on Mac may prefer brew install openclaw-cli for integration with their package manager. Docker is best for servers and isolation. Choose npm when you want a clean, standard Node.js workflow without extra scripts or system packages.

2 Prerequisites: Node.js 22+

OpenClaw requires Node.js 22.0 or later. Check your version with node -v. If you are on an older version, upgrade using nvm, fnm, or your system package manager. On Ubuntu/Debian: curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash - && sudo apt install -y nodejs. On macOS with Homebrew: brew install node@22. On Windows, use the official installer from nodejs.org or WSL2 with a Linux Node.js install.

If you use nvm (Node Version Manager), run nvm install 22 and nvm use 22 before installing OpenClaw. With fnm: fnm install 22 and fnm use 22. This keeps OpenClaw isolated from other projects that may require different Node versions. Ensure npm is available—it ships with Node.js. Verify with npm -v (you need npm 9+).

3 Install OpenClaw

Run:

The -g flag installs OpenClaw globally so the openclaw command is available everywhere. If you get permission errors, use sudo npm install -g openclaw@latest (not ideal) or configure npm to use a user directory: npm config set prefix ~/.local and add ~/.local/bin to your PATH. Verify with openclaw --version.

The install typically takes 30–60 seconds depending on your connection. npm downloads the OpenClaw package from the registry and installs it to your global node_modules. The package includes the CLI binary and dependencies. After installation, the openclaw command should be in your PATH. If it is not found, ensure your npm global bin directory is in PATH. Run npm config get prefix to see where global packages are installed, then add $(npm config get prefix)/bin to your PATH if needed.

4 Run Onboarding

Configure your AI model and messaging channel:

The wizard asks for your AI provider (Claude, OpenAI, Gemini, or Ollama), API key, and a channel (Telegram, Discord, WhatsApp). Have your API key and bot token ready. Use --install-daemon to install a background service (launchd on macOS, systemd on Linux) so OpenClaw starts automatically. If your network blocks AI APIs, connect to a VPN first—a service with 1000Mbps bandwidth ensures fast, reliable API access.

The wizard is interactive: it will prompt you for each setting. For Claude, get an API key from console.anthropic.com; for OpenAI, from platform.openai.com. For Ollama, ensure it is running locally and use http://localhost:11434. For Telegram, create a bot with @BotFather, copy the token, and paste it when asked. After onboarding, send a test message to your bot to confirm everything works. If you see timeouts or connection errors, check that your machine can reach the AI API; a VPN may be required in restricted regions.

5 Platform Notes

macOS: Works on both Apple Silicon and Intel. If you use Homebrew for Node.js, ensure brew --prefix/bin is in your PATH so the global openclaw is found.

Linux: On Ubuntu/Debian, you may need sudo for global installs unless you use a user prefix. systemd service install works out of the box.

Windows: OpenClaw does not run natively on Windows. Use WSL2 (Ubuntu recommended), install Node.js there, then run the npm command. The same binary runs as on Linux.

For Windows users, enable WSL2 and install Ubuntu from the Microsoft Store. Open the Ubuntu terminal, install Node.js 22, then run the npm install. Your OpenClaw config will live in ~/.openclaw inside the WSL filesystem. You can access the Control UI from Windows by opening http://localhost:18789 in your browser. For the daemon, WSL2 supports systemd in recent versions; otherwise, start OpenClaw manually.

6 Updating

To update OpenClaw: npm update -g openclaw. Or reinstall: npm install -g openclaw@latest. If you use the daemon, restart it after updating. The npm package tracks the latest release, so you always get the newest features and fixes.

To pin a specific version, use npm install -g [email protected] (replace with the desired version). This is useful for production where you want to avoid unexpected changes. Check the OpenClaw GitHub releases for version numbers. After updating, run openclaw --version to confirm. Your config in ~/.openclaw is preserved across updates—only the binary changes. If you encounter issues after an update, you can downgrade with npm install -g openclaw@<previous-version>.

Troubleshooting Common Issues

If openclaw is not found after install, check your PATH: echo $PATH should include your npm global bin directory. On macOS with Homebrew Node, run brew link node if needed. For "EACCES" or permission errors, avoid sudo npm when possible—use npm config set prefix ~/.local instead. If the daemon fails to start, check system logs: journalctl -u openclaw on Linux or log show --predicate 'process == "openclaw"' on macOS. For API connection issues, verify your network can reach the AI provider; a VPN with 1000Mbps bandwidth resolves throttling in many regions. The npm package is published by the OpenClaw team and is updated with each release—you can check the changelog on GitHub to see what is new before updating. Many developers prefer npm because it fits into their existing workflow: they use npm for other tools (e.g., VS Code extensions, CLI utilities), and adding OpenClaw is consistent. If you use a monorepo or have multiple Node projects, you can also install OpenClaw as a dev dependency in a specific project, though global install is more common for a system-wide AI assistant. The key takeaway: npm is a first-class install method for OpenClaw, fully supported and recommended for Node.js users.

FAQ