OpenClaw Brew: Complete Installation Guide for Mac Users (2026)

Installing OpenClaw on your Mac doesn't have to be complicated. If you're familiar with Homebrew, the popular package manager for macOS, you already have one of the fastest ways to get OpenClaw up and running. This guide walks you through everything you need to know about using brew to install OpenClaw, from choosing between installation methods to troubleshooting common issues and optimizing your setup.

Quick Answer: OpenClaw brew refers to installing OpenClaw using Homebrew's package manager on macOS. You can use brew install --cask openclaw for the GUI app or brew install openclaw-cli for the command-line version. Both methods install the open-source AI assistant that runs locally on your Mac and integrates with messaging apps, calendars, email, and automation workflows.

What Is OpenClaw Brew and Why Use It?

OpenClaw is an open-source personal AI assistant that runs on your computer and connects to your favorite messaging apps like WhatsApp, Telegram, and Slack. Think of it as having a helpful assistant that can manage your calendar, browse the web, organize files, run terminal commands, and automate repetitive tasks—all while keeping your data local and private.

When we talk about "OpenClaw brew," we're referring to installing this powerful tool using Homebrew, which is the most popular package manager for macOS. Homebrew simplifies software installation by handling dependencies, updates, and configuration automatically.

OpenClaw was created by Peter Steinberger and originally launched under the names Clawdbot and Moltbot before consolidating to OpenClaw in early 2026. It gained over 191,000 GitHub stars in under a week, making it one of the fastest-growing open-source projects in history.

Why Choose Homebrew for OpenClaw Installation?

Using Homebrew to install OpenClaw offers several advantages:

• Automatic dependency management: Homebrew handles Node.js installation and other requirements automatically
• Simple updates: Run brew upgrade openclaw to get the latest version
• Clean uninstallation: Remove OpenClaw completely with brew uninstall
• Familiar workflow: If you already use Homebrew, this fits your existing setup
• Version control: Easily switch between different OpenClaw versions if needed

The Homebrew installation pulled in over 3,800 installs in the first 30 days of 2026, showing strong adoption among Mac users who prefer package managers.

How Do You Install OpenClaw Using Homebrew?

Installing OpenClaw via Homebrew is straightforward, but you'll need to decide which version suits your needs. Here's the complete process from start to finish.

Step 1: Install Homebrew (If You Haven't Already)

First, check if Homebrew is already installed by opening Terminal and running:

brew --version

If you see version information, you're good to go. If not, install Homebrew with this command:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

The installer will guide you through the setup process. Follow the on-screen instructions, and make sure to add Homebrew to your PATH as directed at the end of installation.

Step 2: Update Homebrew

Before installing OpenClaw, update Homebrew to ensure you get the latest package definitions:

brew update

This refreshes the list of available packages and their versions.

Step 3: Choose Your Installation Method

Now comes the important decision: cask or CLI? We'll cover the differences in detail in the next section, but here are the commands:

For the GUI Application (Recommended for Most Users):

brew install --cask openclaw

This installs OpenClaw.app into your Applications folder and requires macOS 15 or later. The current version as of March 2026 is 2026.3.2.

For the Command-Line Interface:

brew install openclaw-cli

This installs the CLI tool globally, which was formerly known as clawdbot-cli. It automatically pulls Node.js 25 as a dependency if you don't already have a compatible version.

Step 4: Launch and Configure OpenClaw

After installation completes:

For the Cask (GUI) Version:

1. Open Spotlight (Cmd + Space)
2. Type "OpenClaw" and press Enter
3. The app launches and guides you through onboarding

For the CLI Version:

1. Open Terminal
2. Run openclaw dashboard to open the browser interface at http://127.0.0.1:18789/
3. Follow the onboarding wizard to configure authentication and gateway settings

The onboarding process walks you through:

• Choosing between local or remote gateway hosting
• Connecting your AI provider (Anthropic API key for Claude, or other LLM options)
• Setting up messaging channels like WhatsApp, Telegram, or Slack
• Configuring security settings and permissions

Should You Use brew install --cask openclaw or brew install openclaw-cli?

This is one of the most common questions from new users. The answer depends on how you plan to use OpenClaw and your comfort level with command-line tools.

Understanding Casks vs Formulae

In Homebrew terminology:

• Formulae install command-line tools and libraries into /usr/local/bin
• Casks install macOS GUI applications into /Applications

Both provide access to the same OpenClaw AI assistant, but they offer different interfaces and workflows.

OpenClaw Cask (GUI Application)

Best for:

• Mac users who prefer graphical interfaces
• People new to terminal-based tools
• Those who want the easiest setup experience

Features:

• Native macOS app with menu bar integration
• Built-in chat interface for interacting with the AI
• Optional CLI installation from within the app
• Visual configuration panels
• Requires macOS 15 or later

Installation size: Approximately 180 MB

The cask version provides the full OpenClaw experience with a polished interface. You can still access terminal functionality—the app optionally installs the global openclaw CLI command so you can use both the GUI and terminal workflows.

OpenClaw CLI (Command-Line Interface)

Best for:

• Developers and power users comfortable with the terminal
• Server or headless Mac environments
• Automation scripts and workflows
• Users who want minimal resource usage

Features:

• Runs as a background service (daemon) using launchd
• Access via terminal commands like openclaw status, openclaw doctor, openclaw dashboard
• Browser-based UI available at localhost:18789
• Lighter footprint than the GUI app
• Works on older macOS versions (macOS 12+)

Installation size: Approximately 45 MB

The CLI version installs OpenClaw as a system service that runs in the background. You interact with it primarily through terminal commands or the browser interface.

Comparison Table

Feature	Cask (GUI)	CLI (Formula)
Installation command	brew install --cask openclaw	brew install openclaw-cli
Interface type	Native macOS app	Terminal + Browser
macOS requirement	15+	12+
Installation size	~180 MB	~45 MB
Menu bar integration	Yes	No
Background service	Yes	Yes
Terminal access	Optional	Built-in
Best for	General users	Developers
Update command	brew upgrade --cask openclaw	brew upgrade openclaw-cli

Can You Install Both?

Yes, you can install both the cask and CLI versions simultaneously. They use different paths and won't conflict. This gives you flexibility to use the GUI when convenient and the CLI for scripting or automation.

However, for most users, choosing one or the other is sufficient. The cask includes everything most people need.

What Are the Prerequisites Before Installing OpenClaw via Brew?

Before running the brew install command, make sure your system meets these requirements and you understand what OpenClaw needs to function.

System Requirements

Operating System:

• macOS 12 (Monterey) or later for openclaw-cli
• macOS 15 (Sequoia) or later for openclaw cask
• Apple Silicon (M1/M2/M3/M4) or Intel processors supported

Hardware:

• At least 4 GB of available RAM (8 GB recommended)
• 500 MB free disk space for installation
• Internet connection for initial setup and API-based AI models

Software Dependencies:

OpenClaw requires Node.js 22 or higher. The Homebrew formula automatically installs Node.js 25 as a dependency, so you don't need to install it separately. However, if you already have an older Node.js version installed via other means (like nvm), you might encounter conflicts.

To check your current Node.js version:

node --version

If you see v22.x.x or higher, you're ready. If you see an older version, let Homebrew handle the installation—it will use its own Node.js version without affecting your existing setup.

Required Accounts and API Keys

OpenClaw is model-agnostic, meaning you can use different AI providers. However, you'll need at least one of the following:

Cloud AI Providers (Choose One):

• Anthropic API key (for Claude models—recommended)
• OpenAI API key (for GPT models)
• Google AI API key (for Gemini models)
• Any OpenAI-compatible API endpoint

Or Local AI Models:

• Ollama installation for running models like Llama or Mistral locally
• vllm-mlx for optimized Apple Silicon performance

You can configure your AI provider during the onboarding wizard after installation. If you plan to use OpenClaw for business automation like building multichannel support bots, having a reliable API key with sufficient credits is important.

Permissions You'll Need to Grant

During setup, OpenClaw will request various macOS permissions:

• Accessibility access: Required for certain automation features
• Full Disk Access: Optional, but needed if you want OpenClaw to access all files
• Network access: Required for AI model communication
• Calendar and Contacts: Optional, needed for calendar management features

You can grant these permissions incrementally as you use different features rather than all at once.

How Do You Troubleshoot Common OpenClaw Brew Installation Errors?

Even with Homebrew's automated installation, you might encounter issues. Here are the most common problems and their solutions.

Error: "brew not installed" or Command Not Found

This happens when Homebrew isn't in your system PATH.

Solution:

After installing Homebrew, you need to add it to your shell profile. For Apple Silicon Macs:

echo 'eval "$(/opt/homebrew/bin/brew shellenv)"' >> ~/.zprofile
eval "$(/opt/homebrew/bin/brew shellenv)"

For Intel Macs:

echo 'eval "$(/usr/local/bin/brew shellenv)"' >> ~/.zprofile
eval "$(/usr/local/bin/brew shellenv)"

Restart your terminal after running these commands.

Error: OpenClaw Requires macOS 15 or Newer

This error appears when trying to install the cask version on an older macOS.

Solution:

You have two options:

1. Install the CLI version instead (works on macOS 12+):

   brew install openclaw-cli
   

2. Upgrade your macOS if your hardware supports it

The CLI version provides the same functionality as the cask—you just access it through the browser interface instead of a native app.

Error: Node.js Version Incompatibility

If you see errors about Node.js version mismatches, this typically happens when you have multiple Node.js installations.

Solution:

Check which Node.js Homebrew installed:

/opt/homebrew/bin/node --version  # Apple Silicon
/usr/local/bin/node --version     # Intel

If you're using nvm or another Node version manager, temporarily disable it or create a shell alias to use Homebrew's Node.js for OpenClaw:

alias openclaw="/opt/homebrew/bin/node $(which openclaw)"

Error: Permission Denied During Installation

This usually means Homebrew doesn't have write access to required directories.

Solution:

Run Homebrew's diagnostic tool:

brew doctor

This identifies permission issues. Follow the suggested fixes, which typically involve:

sudo chown -R $(whoami) /opt/homebrew  # Apple Silicon
sudo chown -R $(whoami) /usr/local     # Intel

Never run brew install with sudo—Homebrew is designed to work without root privileges.

Error: OpenClaw Gateway Won't Start

After installation, if the OpenClaw gateway service fails to start, check the logs.

Solution:

For CLI installations, check the service status:

openclaw status --all

This provides a diagnostic report. Common issues include:

• Port 18789 already in use: Another service is using OpenClaw's default port
• Missing API key: You didn't configure an AI provider during onboarding
• Firewall blocking: macOS firewall is preventing local connections

Run the built-in diagnostic tool:

openclaw doctor --fix

This automatically repairs common configuration issues.

Issue: OpenClaw Running Under Rosetta on Apple Silicon

If you notice slow performance and run:

file $(which openclaw)

And see "x86_64" architecture, OpenClaw is running through Rosetta translation instead of natively.

Solution:

This happens if you installed Homebrew for Intel before getting your Apple Silicon Mac. Reinstall Homebrew for Apple Silicon:

# Uninstall Intel Homebrew
/usr/local/bin/brew uninstall openclaw-cli

# Install Apple Silicon Homebrew (if not already)
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

# Reinstall OpenClaw
brew install openclaw-cli

Verify the architecture:

file $(which openclaw)
# Should show "arm64" for native Apple Silicon

Native Apple Silicon performance is significantly faster, especially for local AI models.

What Security Settings Should You Configure After Installing OpenClaw?

Security should be your top priority when running an AI assistant with access to your files, messages, and system commands. Here's how to properly secure your OpenClaw installation.

Run a Security Audit First

OpenClaw includes a built-in security audit command that identifies common vulnerabilities:

openclaw security audit

This flags issues like:

• Gateway authentication exposure
• Overly permissive file access
• Public network binding
• Unsafe tool permissions

To automatically fix what it can:

openclaw security audit --fix

Review any issues it can't auto-fix and address them manually.

Bind Gateway to Localhost Only

By default, OpenClaw should bind to 127.0.0.1 (localhost), which means only applications on your Mac can connect. Verify this setting:

openclaw config get gateway.bind

If you see 0.0.0.0 or a public IP address, this is a critical security risk—anyone on your network could potentially access your OpenClaw instance.

Fix it immediately:

openclaw config set gateway.bind 127.0.0.1
openclaw restart

Never use 0.0.0.0 unless you fully understand the implications and have additional authentication in place.

Set Up Execution Approvals for Sensitive Tools

OpenClaw can run terminal commands, delete files, and push to git repositories. You should require manual approval for potentially destructive operations.

Edit your OpenClaw configuration file:

open ~/.openclaw/openclaw.json

Add execution approval rules:

{
  "tools": {
    "requireApproval": [
      "terminal",
      "filesystem_delete",
      "git_push",
      "filesystem_write"
    ]
  }
}

This forces OpenClaw to ask permission before executing these commands, preventing accidental data loss or unauthorized actions.

Configure File Access Permissions Properly

Limit which directories OpenClaw can access. By default, it can read most of your home directory, which might be more access than necessary.

Best practice:

1. Create a dedicated workspace directory:

   mkdir ~/openclaw-workspace
   

2. Configure OpenClaw to primarily work in this directory

3. Use macOS Full Disk Access permissions selectively—don't grant it unless you specifically need OpenClaw to access protected locations

Secure Your Configuration Files

Your OpenClaw configuration contains sensitive information like API keys. Protect these files:

chmod 700 ~/.openclaw
chmod 600 ~/.openclaw/openclaw.json

This ensures only your user account can read these files—not other users on your Mac or any processes running without your permissions.

Enable Authentication for Messaging Channels

If you connect OpenClaw to messaging platforms, use authentication and allowlists to control who can interact with your assistant.

For example, when setting up WhatsApp or Telegram integration, configure:

• DM pairing: Require explicit pairing before accepting commands
• User allowlists: Only respond to specific phone numbers or usernames
• Group allowlists: Only activate when mentioned in approved groups

This prevents unauthorized users from sending commands to your AI assistant.

Regular Security Maintenance

Security isn't one-and-done. Make these part of your routine:

Weekly:

• Run openclaw security audit to check for new issues
• Review logs for suspicious activity: openclaw logs --recent

After Updates:

• Rerun security audit after upgrading OpenClaw
• Verify configuration hasn't reset to defaults

Monthly:

• Rotate API keys if possible
• Review which skills and tools are enabled
• Check for unused permissions you can revoke

Many users who implement OpenClaw for practical workflows like triaging sales conversations or e-learning assistance need to be especially careful about data access and security boundaries.

How Do You Optimize OpenClaw Performance on Apple Silicon Macs?

If you're running OpenClaw on an M1, M2, M3, or M4 Mac, you can significantly improve performance with these optimizations.

Verify Native ARM64 Architecture

First, confirm OpenClaw is running natively, not through Rosetta:

file $(which openclaw)

You should see "arm64" in the output. If you see "x86_64," follow the reinstallation steps in the troubleshooting section above.

Native execution runs 2-3x faster for most operations and uses less battery power.

Use vllm-mlx for Local Models

If you want to run AI models locally on your Mac instead of using cloud APIs, vllm-mlx is optimized specifically for Apple Silicon's Metal Performance Shaders.

Why vllm-mlx matters:

• Prefix caching: Caches repetitive prompt prefixes, reducing time-to-first-token from 30-90 seconds to 1-3 seconds on long contexts
• Metal acceleration: Uses Apple's GPU efficiently
• Memory optimization: Better memory management for larger models

Install vllm-mlx:

pip install vllm-mlx

Then configure OpenClaw to use it for local model inference. The performance improvement is particularly noticeable when working with automation tasks that involve repeated context, such as monitoring competitors or managing CRM data.

Configure Reasoning Depth Appropriately

OpenClaw supports different reasoning depths that balance speed versus thoroughness:

• Low: Fast responses, minimal chain-of-thought
• Medium: Balanced—good for most tasks
• High: Deep analysis, uses more tokens and time

Set the default reasoning level in your configuration:

openclaw config set reasoning.depth medium

Use low for simple tasks like scheduling and high for complex problem-solving. Medium works well for most day-to-day automation.

Optimize launchd Service Configuration

On macOS, OpenClaw runs as a launchd service. You can optimize its resource usage by editing the service configuration.

Check your current service config:

cat ~/Library/LaunchAgents/ai.openclaw.plist

After updating OpenClaw via Homebrew, the service might point to an old binary path. Regenerate it:

openclaw service install --force

This ensures the launchd plist points to the current Homebrew-installed binary and uses the latest configuration defaults.

Manage Environment Variables for Mac Services

OpenClaw gateway runs as a launchd service in its own context, which means it doesn't inherit your terminal's environment variables by default.

If you need to set environment variables (like API keys or proxy settings), use launchctl:

launchctl setenv ANTHROPIC_API_KEY "your-key-here"

For persistence across restarts, add them to ~/.zprofile or create a dedicated LaunchAgent plist with environment variable definitions.

What's the Difference Between Homebrew and the Installer Script Method?

You might have seen references to OpenClaw's installer script and wonder how it compares to the Homebrew installation we've been discussing.

The Official Installer Script

OpenClaw provides a one-line installer:

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

This script:

• Detects your operating system
• Checks for Node.js 22+ and installs it if missing
• Installs the OpenClaw CLI globally via npm
• Launches the onboarding wizard automatically
• Configures the background service

When to Use the Installer Script

The installer script is recommended when:

You're on a fresh system: The script handles all dependencies from scratch, making it ideal for new setups

You're deploying to a VPS or cloud server: The docs specifically recommend using a clean base OS image with the installer script for remote deployments

You don't use Homebrew: If you prefer npm-based installations or don't want to install Homebrew, the installer script is simpler

You want the guided onboarding immediately: The script launches configuration wizards automatically without additional commands

When to Use Homebrew Instead

Homebrew is better when:

You already use Homebrew for package management: Keeps all your tools in one ecosystem

You want easier updates: brew upgrade is simpler than managing npm global packages

You prefer the cask (GUI) version: Only available through Homebrew, not the installer script

You need version pinning: Homebrew makes it easier to stay on specific versions or roll back

You want automatic dependency resolution: Homebrew's dependency graph handles complex scenarios better

Comparison Table: Homebrew vs Installer Script

Aspect	Homebrew	Installer Script
Installation command	brew install openclaw-cli	curl ... | bash
Handles Node.js	Yes, automatically	Checks and prompts
GUI app available	Yes (via cask)	No
Updates	brew upgrade openclaw-cli	npm update -g openclaw
Uninstall	brew uninstall openclaw-cli	npm uninstall -g openclaw
Onboarding wizard	Manual: openclaw dashboard	Automatic after install
Best for	Mac users with Homebrew	Fresh systems, servers
Dependency management	Homebrew ecosystem	npm ecosystem

Can You Switch Between Methods?

Yes, you can uninstall one method and reinstall with another. Your configuration files in ~/.openclaw/ are preserved across different installation methods.

To switch from installer script to Homebrew:

# Uninstall npm version
npm uninstall -g openclaw

# Install via Homebrew
brew install openclaw-cli

Your settings, API keys, and message history remain intact.

How Do You Update OpenClaw Installed via Homebrew?

Keeping OpenClaw updated ensures you get the latest features, security patches, and bug fixes. Here's how to manage updates when using Homebrew.

Check for Available Updates

First, update Homebrew's package index:

brew update

Then check if OpenClaw has a newer version available:

brew outdated

If you see openclaw or openclaw-cli in the list, an update is available.

Update OpenClaw CLI

For the command-line version:

brew upgrade openclaw-cli

This downloads and installs the latest version while preserving your configuration.

Update OpenClaw Cask (GUI)

For the GUI application:

brew upgrade --cask openclaw

Note the --cask flag—it's required for cask applications.

Update All Homebrew Packages

If you want to update OpenClaw along with all your other Homebrew packages:

brew upgrade

This updates everything that's outdated, which can be convenient but might update packages you want to keep pinned.

Verify the Update

After updating, verify the new version:

openclaw --version

You should see the latest version number (as of March 2026, the current release is 2026.3.2 for the cask and 2026.2.26 for the CLI).

Restart OpenClaw Gateway

After updating, restart the OpenClaw gateway to use the new version:

openclaw restart

If you updated via the cask, you can also quit and reopen the OpenClaw application.

Handle Breaking Changes

Occasionally, updates include breaking changes that require configuration adjustments. Always check the release notes:

brew info openclaw-cli

Look for any "Caveats" section that describes changes you need to make.

If an update causes issues, you can roll back to the previous version:

# Uninstall current version
brew uninstall openclaw-cli

# Install specific older version (example)
brew install [email protected]

Enable Automatic Updates (Optional)

You can set up automatic Homebrew updates using a launchd schedule or cron job, but this isn't recommended for critical production systems where you want to control when updates happen.

For personal use, adding this to your shell profile keeps things fresh:

# Add to ~/.zshrc
alias brewup='brew update && brew upgrade && brew cleanup'

Then periodically run brewup to update everything at once.

Frequently Asked Questions

Is OpenClaw free, or do I need to pay for it?

OpenClaw itself is completely free and open-source under the MIT license. However, you'll need to pay for AI model access—either through API providers like Anthropic (Claude) or OpenAI (GPT), or by running models locally on your hardware. The Homebrew installation doesn't include any built-in costs; you just bring your own API key.

Can I use OpenClaw without an internet connection?

Partially. OpenClaw can run entirely offline if you use local AI models through Ollama or vllm-mlx instead of cloud APIs. However, the initial installation via Homebrew requires internet connectivity to download packages. Messaging integrations like WhatsApp and Telegram also need internet access, but local file operations and terminal commands work offline with local models.

How much does OpenClaw cost to run per month?

The cost depends entirely on your AI provider usage. If you use Anthropic's Claude API, expect to pay based on tokens consumed—typically $0.25-$3 per million input tokens depending on the model. For light personal use, many users spend $5-20/month. Heavy automation might cost $50-200/month. Local models are free to run but require capable hardware (at least 16 GB RAM for 7B parameter models, 32 GB+ for larger models).

Does OpenClaw work with non-Mac computers?

Yes, OpenClaw supports Windows and Linux in addition to macOS. However, Homebrew is Mac-specific. On Linux, you can use Linuxbrew or the installer script. On Windows, use WSL (Windows Subsystem for Linux) with the installer script. The Homebrew installation method we've discussed in this guide is specifically for macOS users.

What's the difference between OpenClaw and ChatGPT?

ChatGPT is a web-based chat interface for OpenAI's GPT models. OpenClaw is a self-hosted AI assistant that connects to various AI models (including GPT if you want) and integrates with your local system, files, calendars, email, and messaging apps. OpenClaw can execute commands, automate workflows, and maintain conversation history locally. ChatGPT is simpler but less powerful for automation.

Will OpenClaw slow down my Mac?

OpenClaw uses minimal resources when idle—typically 50-150 MB of RAM for the background service. When actively processing requests, resource usage depends on whether you're using cloud APIs (minimal local compute) or local models (can use significant RAM and GPU). On modern Macs with 16 GB+ RAM, you likely won't notice any performance impact during normal use.

Wrapping Up: Your Next Steps with OpenClaw Brew

Installing OpenClaw via Homebrew gives you a powerful, locally-controlled AI assistant that integrates seamlessly with your Mac workflow. Whether you chose the cask for its polished GUI or the CLI for its flexibility, you now have a foundation for serious automation.

Here's what to do next:

1. Run the security audit to ensure your installation is properly locked down
2. Connect your first messaging channel (WhatsApp, Telegram, or Slack) to test basic functionality
3. Explore the skills marketplace to add pre-built capabilities for specific tasks
4. Start small with simple automation like calendar management or file organization
5. Gradually expand to more complex workflows as you get comfortable

The OpenClaw community is active and helpful—if you run into issues beyond what this guide covers, the GitHub discussions and official documentation are excellent resources.

Remember that OpenClaw is a tool, not magic. The quality of your results depends on how well you configure security settings, choose appropriate AI models, and design your automation workflows. Take time to understand the permissions you're granting and the access you're providing.

With the Homebrew installation complete and properly configured, you have everything you need to start building powerful AI-driven automation on your Mac.