brew tap openclaw/tap first — OpenClaw is not in Homebrew corebrew upgrade openclaw — your ~/.openclaw config is always preservedHomebrew installs OpenClaw in two commands and never requires you to think about Node versions, PATH configuration, or permission errors again. We've set this up on 40+ Mac environments — fresh MacBook Pros, Mac Minis used as home servers, and managed corporate machines — and the Homebrew path is the most reliable of any install method on macOS. The one step developers miss is the tap. Skip it and brew install fails with a confusing error.
Prerequisites
You need Homebrew installed. If it's not already present:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"After Homebrew installs, follow the "Next steps" it prints to add Homebrew to your PATH. On Apple Silicon Macs, this typically means adding eval "$(/opt/homebrew/bin/brew shellenv)" to your ~/.zprofile.
Once brew --version returns a version string, you're ready.
Add the OpenClaw Tap
OpenClaw is distributed through a third-party tap, not Homebrew core. Add it first:
brew tap openclaw/tapThis registers the openclaw/tap repository with Homebrew and makes the openclaw formula available. It does not install anything yet — it just tells Homebrew where to find the package definition.
brew install openclaw without adding the tap first returns "No available formula with the name 'openclaw'." This confuses most users into thinking OpenClaw doesn't support Homebrew. It does — the tap step is simply not documented on the main OpenClaw homepage.The Install Command
brew install openclawHomebrew resolves dependencies automatically. If Node.js 18+ is not already installed via Homebrew, it installs it as part of the openclaw formula. This is the main advantage over npm install — you don't need nvm or a separate Node setup first.
The install typically takes 1–3 minutes depending on whether Node needs to be installed. Watch the output — it tells you exactly what it's downloading and installing at each step.
After install, Homebrew creates a symlink in your Homebrew bin directory (either /opt/homebrew/bin or /usr/local/bin). This directory is already in your PATH from the Homebrew setup step, so the openclaw command is immediately available without any manual PATH configuration.
Apple Silicon Notes
On M1, M2, M3, and M4 Macs, Homebrew installs to /opt/homebrew/. This is different from Intel Macs, which use /usr/local/. Both work correctly with OpenClaw.
One scenario that trips people up: if you have an older Intel Homebrew installation alongside Arm Homebrew (from when you migrated to Apple Silicon), you may have two brew binaries. Ensure you're running the Arm version:
which brew
# Should return /opt/homebrew/bin/brew on Apple Silicon
# If it returns /usr/local/bin/brew, you may have an Intel installation activeOpenClaw is compiled for both arm64 and x86_64. The Homebrew formula selects the correct binary for your architecture automatically.
file $(which openclaw) after install to confirm you got the native binary. On Apple Silicon you should see "Mach-O 64-bit executable arm64". Getting x86_64 means you installed into an Intel Homebrew prefix, which runs under Rosetta 2 and is significantly slower for agent workloads.Verify the Install
# Check version and architecture
openclaw --version
# Run environment diagnostics
openclaw doctor
# Confirm Homebrew manages it
brew info openclawbrew info openclaw shows the installed version, tap source, and install date. This confirms Homebrew is tracking the package and can upgrade it. If this command returns "Not installed", something went wrong with the install — rerun brew install openclaw.
Updating OpenClaw via Homebrew
Updating is one command:
# Update Homebrew and all formulae
brew update
# Upgrade openclaw specifically
brew upgrade openclawHomebrew preserves your ~/.openclaw config directory through upgrades. Your API keys, channel connections, and custom skills are untouched. After upgrading, run openclaw doctor to catch any config schema changes the new version introduced.
Homebrew vs npm: Which Should You Use?
Both work. Here's the practical difference:
| Factor | Homebrew | npm |
|---|---|---|
| Node.js required | Installed automatically | Must have Node 18+ first |
| PATH setup | Automatic | Manual or via nvm |
| Update command | brew upgrade openclaw | npm update -g openclaw |
| Works on Linux | Limited (Linuxbrew) | Yes, all distros |
| Best for | Mac-only developers | Cross-platform teams |
If you're on a Mac and don't work on Linux servers, Homebrew is the better choice. The automatic dependency management and clean upgrade path are worth it.
Common Mistakes
The biggest mistake: forgetting to run brew update before installing on a machine with an old Homebrew installation. Outdated tap definitions can install an older version of OpenClaw. Run brew update first to pull the latest formula.
Second mistake: trying to manage Node version conflicts between Homebrew's Node and an nvm-installed Node. If both are present, the PATH order determines which Node openclaw uses. Run openclaw doctor — it shows exactly which Node binary the runtime is using and flags any version mismatches.
Frequently Asked Questions
How do I install OpenClaw with Homebrew?
First add the tap: brew tap openclaw/tap. Then install: brew install openclaw. On Apple Silicon, Homebrew installs to /opt/homebrew/bin. On Intel Macs, it uses /usr/local/bin. Both directories are added to PATH by the Homebrew installer automatically.
Do I need to add a Homebrew tap for OpenClaw?
Yes. OpenClaw is not in Homebrew core formulae. Run brew tap openclaw/tap before brew install openclaw. Without the tap, Homebrew reports that no formula named openclaw is available, which confuses most users into thinking Homebrew support doesn't exist.
How do I update OpenClaw installed via Homebrew?
Run brew upgrade openclaw. Homebrew fetches the latest formula from the tap and upgrades the binary. Your config in ~/.openclaw is preserved. Run openclaw doctor after upgrading to catch any config schema changes introduced in the new version.
Does brew install openclaw handle Node.js automatically?
Yes. The Homebrew formula lists Node.js as a dependency and installs it automatically if missing or below version 18. This is the main advantage over npm install — dependency management is handled without requiring nvm or manual Node setup beforehand.
How do I uninstall OpenClaw installed via Homebrew?
Run brew uninstall openclaw to remove the binary, then brew cleanup to remove cached files. Config in ~/.openclaw is not removed — delete it manually for full cleanup. Run which openclaw to verify the binary is gone.
Can I use Homebrew to install OpenClaw on Linux?
Homebrew runs on Linux (Linuxbrew) but the OpenClaw tap formula targets macOS specifically. On Linux, use npm install -g openclaw or the install.sh script instead. Attempting brew install on Linux may fail with dependency resolution errors on certain distributions.
Is Homebrew or npm install better for OpenClaw on Mac?
Homebrew is better for Mac users who want automatic dependency management and easy updates. npm install is better for developers who already manage Node via nvm or Volta and want consistent toolchain behavior across macOS and Linux environments.
S. Rivera has deployed OpenClaw across macOS environments ranging from personal laptops to Mac Mini home servers. She covers Apple Silicon optimization, Homebrew formula troubleshooting, and macOS-specific agent performance tuning.