OpenClaw is a local tool that lets your AI agent connect to apps like Telegram or WhatsApp and take action, such as sending messages or handling tasks. Getting it set up is straightforward once you understand the process. This guide covers installation across macOS, Linux, and Windows.
Table of contents
Choose the setup that fits your needs. Running OpenClaw locally keeps everything on your own machine and requires installing dependencies such as npm or using an automated script. If you prefer to skip setup, fully hosted platforms like Kimi Claw handle the environment for you, letting you get started directly.
| macOS / Linux | Windows | |
|---|---|---|
| Run locally | One-line Terminal command | One-line PowerShell command |
| Via npm | Via npm | |
| Via HomeBrew | Via WSL2 | |
| Run online | Cloud-based Solution (e.g., Kimi Claw) | Cloud-based Solution (e.g., Kimi Claw) |
macOS and Linux share the same installer and commands. These instructions apply to both systems unless noted.
Below is a quick setup guide. For a full step-by-step walkthrough with screenshots, see How to install OpenClaw on macOS.
Run the official installer script to set up OpenClaw. The script checks whether Node.js 22 or newer is installed. If it is missing or outdated, Node.js 24 will be installed automatically. It then installs the OpenClaw CLI and launches the onboarding wizard.
Follow the onboarding wizard to set up your agent environment, including selecting a model provider (e.g., Kimi API), entering your API key, choosing a channel, and configuring basic settings.
Run the following command to confirm your OpenClaw version.
Run the following command to check that the OpenClaw gateway is active.
The installer also registers a LaunchAgent on macOS or a systemd service on Linux, so OpenClaw continues running in the background. Once everything is set up, your agent is ready to use. You can start chatting, connect tools, or configure workflows based on your needs.
Use Homebrew to install Node.js by running the following command in Terminal. If Node.js is already installed, run the upgrade command instead to ensure you are using the latest version.
Run the following command to install the OpenClaw CLI globally.
Run the following command to launch the onboarding wizard and register the background daemon. Follow the wizard to configure your agent environment, including selecting a model provider (e.g., Kimi API), entering your API key, and connecting a messaging channel. Once setup is complete, your agent is ready to use. You can start chatting, connect tools, or configure workflows based on your needs.
Run the following command to ensure Node.js 22.14 or later is installed on your system. If your version is up to date, you can proceed with the installation.
Run the following command to install the OpenClaw CLI globally.
Run the following command to start the onboarding wizard and register the background daemon. Follow the wizard to configure your agent environment, including selecting a model provider (e.g., Kimi API), entering your API key, and choosing a messaging channel. Once setup is complete, your agent is ready. You can start interacting with it, connect tools, or build workflows based on your needs.
Platform notes: OpenClaw supports both Intel and Apple Silicon Macs. If the installation is blocked by Gatekeeper, you can allow it in System Settings under Privacy & Security.
Windows offers three main ways to install OpenClaw: the PowerShell installer for a quick native setup, WSL2 for a full Linux environment, and npm for manual installation.
Below is a quick setup guide. For a full step-by-step walkthrough with screenshots, see How to install OpenClaw on Windows.
Open PowerShell as administrator and run the official one-line script to install OpenClaw.
Follow the onboarding steps to configure your agent environment, including selecting a model provider (e.g., Kimi API), entering your API key, and choosing a messaging channel.
Run the following command to confirm that OpenClaw is installed correctly and the gateway is active.
Once setup is complete, your agent is ready. You can start interacting with it, connect tools, or configure workflows based on your needs.
Open PowerShell as administrator and run the following command to enable and initialize WSL2.
Open your Linux terminal and run the standard installation script to install OpenClaw.
Follow the onboarding steps to configure your agent environment, including selecting a model provider (e.g., Kimi API), entering your API key, and choosing a messaging channel.
Once setup is complete, your agent is ready. You can start interacting with it, connect tools, or configure workflows based on your needs.
Run the following command to verify that Node.js is installed and up to date.
Run the following command to install the OpenClaw CLI globally.
Run the following command to start the onboarding wizard and register the background daemon.
Follow the onboarding steps to configure your agent environment, including selecting a model provider (e.g., Kimi API), entering your API key, and choosing a messaging channel.
Once setup is complete, your agent is ready. You can start interacting with it, connect tools, or configure workflows based on your needs.
The methods above require a terminal, a supported Node.js version, and a machine that stays on. Kimi Claw provides a fully hosted option, so you can run OpenClaw without installing or maintaining a local environment.
Go to the Kimi Claw page and click Create to start.
Confirm the deployment in the pop-up window. Kimi Claw will automatically set up your OpenClaw environment, including the gateway and workspace, without requiring any local configuration.
Once deployment is complete, your workspace opens in the dashboard. You can start interacting with your agent, set up skills, configure scheduled tasks, and manage files directly in your browser.
Key features of Kimi Claw
Most OpenClaw installation issues fall into a few common categories, such as PATH configuration, missing dependencies, or port conflicts. The sections below help you quickly identify and fix the most frequent problems across macOS, Windows, and Linux.
OpenClaw is not in your system PATH.
Then reload your shell (e.g., source ~/.zshrc) or restart your terminal. On Windows, add the path to your environment variables and restart PowerShell.
This usually happens when a globally installed libvips conflicts with the Sharp library.
If you see node-gyp errors, install Xcode Command Line Tools:
The background daemon was not installed during onboarding.
Then verify the service:
The gateway process may have stopped, or API authentication may have failed.
Run a health check:
For debugging logs:
Also, verify your API key is valid.
Another process is using the OpenClaw gateway port.
Then restart the gateway:
This usually means the npm global directory does not have the correct permissions.
On Windows, run PowerShell as Administrator or set a custom npm prefix:
For Docker setups, fix volume permissions:
Git is not installed or not available in the PATH.
Systemd is not enabled in your WSL configuration.
/etc/wsl.conf and add.Then restart WSL:
Reopen your Linux terminal and verify:
Low-memory VPS instances may fail during package installation.
Then rerun the installation.
Your account is not authorized by OpenClaw.
Also, verify your bot credentials (token, webhook, permissions) are configured correctly.
Installing OpenClaw is straightforward across macOS, Linux, and Windows. You can use a one-line script, PowerShell, WSL2, or npm, depending on your setup. The onboarding wizard guides you through model selection, API configuration, and messaging channels. If you prefer not to manage a local environment, Kimi Claw offers a fully hosted option that lets you run OpenClaw directly in the cloud.