OpenClaw can be installed on Mac in several ways, depending on how you prefer to work and manage your setup. In this guide, you’ll find step-by-step instructions for different installation methods, along with tips to help you get OpenClaw running smoothly.
Table of contents
Here is a side-by-side comparison of the three methods. Each differs in how much manual setup you need to handle.
| One-Line Installer | Homebrew | Kimi Claw (Online) | |
|---|---|---|---|
| What it is | Official install script that downloads and sets up OpenClaw automatically | Manual setup using Homebrew to install dependencies (like Node.js), then running OpenClaw via the CLI | Online tool that lets you run OpenClaw in the cloud without manual setup |
| Manual steps required | Minimal manual steps | Multiple manual steps required | No manual setup required |
| Code or terminal required | Yes | Yes | No |
| 24/7 availability | Only runs while your Mac is awake | Only runs while your Mac is awake | Runs 24/7 in the cloud |
| Best for | First-time users who want the fastest local setup | Developers who prefer managing packages through Homebrew | Users who want to run OpenClaw without local setup |
Kimi Claw lets you run OpenClaw in the cloud without setting up Node.js, Homebrew, or API keys. You can start using a working agent in your browser within minutes.
If you prefer a local setup, continue to the next section. If you want a simpler option, jump to the Run OpenClaw on Mac with Kimi Claw section, or click the button below to get started instantly.
Before installing OpenClaw locally on Mac, there are a few preparation and security steps to complete. If you plan to use Kimi Claw, you can skip this section and go directly to the setup instructions below.
Dependencies: The one-line installer installs Node.js automatically if needed. If you choose Homebrew, you need to install Node.js manually (Node 24 recommended; Node 22 LTS 22.16+ also works).
Firewall and network settings: The macOS firewall is typically off by default. You can enable it in System Settings > Network > Firewall. OpenClaw binds the gateway to 127.0.0.1 (localhost), so other devices on your network cannot connect to it directly. If you need mobile or remote access, you can use tools like Tailscale or an SSH tunnel. Do not forward port 18789 through your router.
This is the fastest way to run OpenClaw locally on Mac. OpenClaw runs from the Terminal and provides a browser-based interface for managing your agent, rather than a traditional graphical app. A single command installs the CLI, checks your Node.js version, and launches the onboarding wizard.
Open Terminal using Spotlight (⌘ + Space), then paste the following command:
The script detects your system, installs the OpenClaw CLI, and checks your Node.js version. If Node.js is missing or outdated, it installs Node 24 automatically (Node 22 LTS 22.16+ is also supported).
The onboarding wizard starts automatically after the install finishes. Select Moonshot AI (Kimi K2.5) as your LLM provider and paste your Kimi API key when prompted. Accept the default settings for the gateway port and authentication. If you want OpenClaw to start automatically when your Mac boots, choose the daemon installation option during onboarding.
Run the following command to check that the gateway is running:
Then open the dashboard:
This command opens the Control UI in your browser at http://127.0.0.1:18789. Enter your gateway token to log in. Once logged in, you can start interacting with your OpenClaw agent.
If you prefer managing packages with Homebrew, you can install OpenClaw on Mac using a more manual setup. This method gives you more control over dependencies and fits into your existing Homebrew workflow.
Open Terminal using Spotlight (⌘ + Space). If you don’t have Homebrew installed, run the following command. Homebrew is a package manager for macOS that lets you install and manage developer tools from the Terminal, similar to how an app store installs apps.
During installation, you may be prompted to enter your Mac login password. Note that Terminal will not display any characters as you type for security reasons. You may also see prompts to confirm installation and messages showing files being installed.
Once installation is complete, you’ll see a success message and the next steps in the Terminal.
Once Homebrew is installed, install Node.js:
After installation, confirm the version is v24 (recommended) or v22.16+.
Install the CLI globally with npm, then run onboarding:
If you see an EACCES permission error during npm install -g, your npm global directory needs elevated access. Either run sudo npm install -g openclaw@latest, or change your npm default directory to avoid using sudo in the future.
The --install-daemon flag registers OpenClaw as a LaunchAgent, so the gateway starts automatically when you log in. During onboarding, select Moonshot AI (Kimi K2.5) as your provider and enter your Kimi API key.
Verify that the gateway is running and open the dashboard:
The Control UI opens in your browser. Enter your gateway token, and you are ready to go.
Kimi Claw is an online tool that lets you run OpenClaw in the cloud without local setup. There’s nothing to install on your Mac, and you don’t need to use the Terminal or manage dependencies. Everything runs in your browser. You can create an OpenClaw agent in minutes. Kimi Claw handles the gateway, workspace, storage, and model access, so your agent stays online 24/7, even when your MacBook is closed.
Go to the Kimi Claw page and click Create to start deploying your OpenClaw environment.
Confirm the deployment in the pop-up window. Kimi Claw then sets up the OpenClaw environment, including the gateway, workspace, and tools. The process usually finishes within a few minutes.
Once deployment finishes, your workspace opens in the dashboard. Start chatting with your agent, set up skills, schedule tasks, and manage files, all from the browser.
Kimi Claw provides a simpler way to run OpenClaw without local setup. Instead of installing dependencies and managing a local environment, you can run your agent directly in the browser while Kimi Claw handles the underlying setup and infrastructure.
No local setup required: Run OpenClaw without installing Node.js or using the Terminal. Everything works directly in your browser, so you can get started faster and avoid environment setup issues.
Instant access to 5,000+ skills: Instead of installing tools manually, Kimi Claw can automatically use the skills needed for your task from a large library of available tools, reducing setup time and compatibility issues.
Always-on automation & scheduling: Unlike local agents that stop when your Mac sleeps, Kimi Claw runs 24/7 in the cloud, making it suitable for scheduled tasks and long-running workflows.
40GB cloud storage & persistent memory: Unlike local setups, where files are typically tied to a single device, Kimi Claw includes 40GB of storage, making your reports and research accessible from any browser. It also remembers your preferences and work context across sessions, so you can continue where you left off.
Integrated Kimi K2.5 model and pro-grade search: Kimi Claw comes with built-in access to Kimi K2.5 and advanced search capabilities, so you don’t need to manage API keys or set up external services. It can automatically bring in up-to-date information across areas such as finance, technology, and news, making research and task execution more seamless.
Most users treat AI like a traditional desktop app. You use it while you’re at your desk and close it when you’re done. For valuable automation, like monitoring global markets overnight or having a research report ready in your inbox by 8 AM, your agent needs to stay active around the clock. Since macOS naturally pauses local processes when the system sleeps, achieving this requires a specific strategy. This section covers two ways to maintain a persistent connection:
Option A: Dedicated Mac hardware
One option is to keep a Mac (such as a Mac mini) running continuously. You can disable sleep using sudo pmset -a sleep 0 and enable “Wake for network access” in System Settings. For remote access, you can use tools like Tailscale or an SSH tunnel.
This setup keeps OpenClaw running on your own hardware, but it requires keeping your machine powered on and handling maintenance, updates, and restarts yourself.
Option B: Kimi Claw handles this automatically
If you run your agent with Kimi Claw, 24/7 availability is built in. Your agent runs independently of your local device, so it continues working even when your Mac is closed or offline. There’s no need to adjust sleep settings or keep a machine running.
Even with a simple setup, you may run into issues during installation. Here are some common problems and how to fix them.
Cause: The npm global bin directory is not in your shell PATH.
Fix: Run source ~/.zshrc to reload your shell configuration. If you use Bash instead of Zsh, replace ~/.zshrc with ~/.bash_profile. If the error persists, find your npm prefix and add it to PATH:
Cause: The LaunchAgent was not installed during onboarding.
Fix: Run the onboarding command with the daemon flag:
This registers a LaunchAgent that starts the OpenClaw gateway automatically when you log in. To verify it is active:
18789 is already in use Cause: Another process is occupying the gateway port.
Fix: Find and stop the conflicting process:
Cause: Some npm packages require native compilation, and the Xcode Command Line Tools are missing or outdated.
Fix: Install or update the tools:
After installation completes, retry installing the skill.
Cause: Your Mac has Node.js installed that is older than 22.16. OpenClaw requires Node 24 (recommended) or Node 22 LTS 22.16+.
Fix: If you used Homebrew:
If you used the one-line installer, re-run it. The script will detect the outdated version and update it.
OpenClaw can run locally on your Mac using the one-line installer or Homebrew, or in your browser with Kimi Claw without local setup. Each method leads to a working agent, but requires a different level of manual effort. If you want a faster setup with 24/7 availability built in, you can start with Kimi Claw and have your agent running within minutes.
openclaw onboard --install-daemon to register a LaunchAgent that starts the gateway on login. If the daemon is already installed but not starting, check its status with launchctl list | grep openclaw and review the system logs. Kimi Claw users do not need this configuration because the service runs on cloud servers and stays online independently.source ~/.zshrc to reload the configuration. If the command is still not found, run npm config get prefix to locate the bin directory and add it to your PATH in ~/.zshrc. Restart Terminal after making the change.sudo pmset -a sleep 0) and remote access via Tailscale, or use Kimi Claw. Kimi Claw is a fully managed platform that keeps your OpenClaw agent online around the clock, with no hardware to maintain.curl -fsSL https://openclaw.ai/install.sh | bash. The script installs OpenClaw, checks your Node.js version, and walks you through setup. You can also use Homebrew: run brew install node, then npm install -g openclaw@latest. For a fully managed option that requires no terminal, Kimi Claw runs OpenClaw in your browser, with no local setup.curl -fsSL https://openclaw.ai/install.sh | bash) or install through Homebrew with npm install -g openclaw@latest. For a browser-based option that requires no download, Kimi Claw runs OpenClaw for you on cloud servers.