OpenClaw Install Mac: The Complete Setup Guide That Actually Works

Getting OpenClaw running on Mac takes under 10 minutes when you know the two steps that trip up 80% of first-timers. The Gatekeeper security block and a misconfigured PATH are responsible for nearly every failed install we see in the community. Solve those first, and everything else is straightforward.

System Requirements

OpenClaw runs on macOS 12 Monterey, 13 Ventura, and 14 Sonoma. If you're on an older version, the binary may still work but you're outside the tested range. Upgrade macOS first — it's not worth debugging on unsupported versions.

Minimum specs: 4GB RAM and 500MB free disk space. In practice, your agents will use more RAM depending on the LLM you're routing to and how many concurrent sessions you run. A modern Mac with 8GB RAM handles 3–5 agents comfortably.

Install via Homebrew (Recommended)

Homebrew is the recommended install path. It handles the PATH configuration automatically, makes updates trivial, and installs the correct binary for your architecture without any manual steps.

If you don't have Homebrew installed, get it first. We'll get to the exact config in a moment — but first make sure Homebrew itself is working before adding OpenClaw on top of it.

# Install Homebrew if you don't have it
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

# Install OpenClaw
brew install openclaw

# Verify the install
openclaw --version

That's the entire Homebrew process. The brew install command downloads the correct binary for your Mac (Intel or Apple Silicon), places it on your PATH, and sets up any required dependencies. No quarantine issues, no PATH editing.

Manual Binary Install

Prefer not to use Homebrew? Download the binary directly from the OpenClaw releases page. Choose the correct file for your architecture: openclaw-darwin-arm64 for Apple Silicon, openclaw-darwin-amd64 for Intel.

# Download the binary (replace with latest version)
curl -LO https://github.com/openclaw/openclaw/releases/latest/download/openclaw-darwin-arm64

# Make it executable
chmod +x openclaw-darwin-arm64

# Move to a directory on your PATH
sudo mv openclaw-darwin-arm64 /usr/local/bin/openclaw

# Remove the Gatekeeper quarantine flag
xattr -d com.apple.quarantine /usr/local/bin/openclaw

# Verify
openclaw --version

The xattr command is the step most people miss. Without it, macOS refuses to run the binary and shows a cryptic "developer cannot be verified" error. This command removes the quarantine attribute specifically — it doesn't disable Gatekeeper or change any system security settings.

PATH Configuration

If openclaw --version returns "command not found" after installing the binary, your PATH doesn't include the installation directory. Fix it by adding the directory to your shell profile.

# For zsh (default on macOS Catalina and later)
echo 'export PATH="/usr/local/bin:$PATH"' >> ~/.zshrc
source ~/.zshrc

# For bash (if you're still using it)
echo 'export PATH="/usr/local/bin:$PATH"' >> ~/.bash_profile
source ~/.bash_profile

# Confirm openclaw is found
which openclaw

After sourcing your profile, which openclaw should return the full path to the binary. If it still doesn't, open a new terminal window — some shell changes only take effect in new sessions.

First Run and Verification

With the binary on your PATH, run the doctor command. This checks all dependencies, validates your configuration directory, and tests connectivity to any LLM endpoints you've configured.

# Run the diagnostics check
openclaw doctor

# Initialize default config if this is a fresh install
openclaw init

# Start the gateway
openclaw gateway start

A clean openclaw doctor output looks like this: all green checkmarks, no warnings about missing dependencies or unreachable endpoints. If you see red items, fix them before proceeding — running agents on a broken installation creates confusing error messages that are harder to debug later.

Sound familiar? The openclaw init command creates ~/.config/openclaw/config.yaml with sensible defaults. Open that file and add your LLM API key before starting the gateway. Without a valid API key, agents will connect but fail on every message.

Common Installation Mistakes

• Skipping the quarantine removal — the "cannot be verified" Gatekeeper dialog is not a permanent block. Run xattr -d com.apple.quarantine /usr/local/bin/openclaw and the binary works immediately.
• Installing the wrong architecture binary — x86_64 runs on Apple Silicon via Rosetta but performs worse. Always check uname -m and download the matching binary.
• Not running openclaw init before gateway start — the gateway needs a config file to start. Without init, it throws a confusing "config not found" error on first run.
• Putting the binary in a non-standard location — placing it in ~/Downloads or your Desktop means the PATH won't include it. Always move binaries to /usr/local/bin or /opt/homebrew/bin.
• Running sudo openclaw for everything — the gateway and agents should run as your user, not root. Running as root changes where config files are read from and can cause permission errors on agent workspaces.

Frequently Asked Questions

What are the system requirements to install OpenClaw on Mac?

OpenClaw requires macOS 12 Monterey or later, at least 4GB RAM, and 500MB free disk space. Apple Silicon Macs run the native ARM binary without Rosetta. An internet connection is needed for the initial download and for LLM API calls your agents make during operation.

Can I install OpenClaw on Mac without Homebrew?

Yes. Download the macOS binary directly from the releases page, make it executable with chmod +x, and move it to /usr/local/bin. Then remove the quarantine flag with xattr -d com.apple.quarantine. Both Homebrew and manual installs produce identical results.

Why does OpenClaw fail to open on Mac with a security warning?

macOS Gatekeeper blocks unsigned binaries. Run xattr -d com.apple.quarantine /usr/local/bin/openclaw to remove the quarantine flag. This targets the specific file only — it does not disable Gatekeeper system-wide or reduce your Mac's security posture.

Where does OpenClaw store its config files on Mac?

Configuration lives in ~/.config/openclaw/ by default. The main config file is ~/.config/openclaw/config.yaml. Override this location by setting the OPENCLAW_CONFIG environment variable to any directory path you prefer.

How do I update OpenClaw on Mac?

With Homebrew: run brew upgrade openclaw. For manual installs, download the latest binary and replace the existing file. Your config files in ~/.config/openclaw/ are never touched during upgrades — settings persist across all versions automatically.

How do I verify my OpenClaw Mac installation worked correctly?

Run openclaw --version to confirm the binary is on your PATH. Then run openclaw doctor to check all dependencies and connectivity. A passing doctor check means your installation is complete and agents can start running immediately.