Fix OpenClaw brew not installed
brew not installed errors block the Homebrew-based OpenClaw installation path on macOS. This guide covers both fixing Homebrew and using alternative installation paths that bypass it entirely.
Check if Homebrew is actually installed
Homebrew installs to different locations depending on whether you are on Intel or Apple Silicon. On Intel Macs, the installation path is /usr/local/bin/brew. On Apple Silicon, it installs to /opt/homebrew/bin/brew. If brew --version returns command not found, Homebrew is not installed or its bin directory is not in your PATH.
Open a new terminal window and run brew --version. If the command is not found but you believe Homebrew was previously installed, your shell profile may have failed to load the brew initialization script. Check ~/.zshrc, ~/.bash_profile, and ~/.zprofile for lines that add Homebrew to PATH.
A common cause of apparent brew installation failures is running the installation script on an Apple Silicon Mac but using the Intel installation instructions, or vice versa. The Apple Silicon installation requires Rosetta 2 for some older brew packages but the brew binary itself runs natively.
- Run brew --version in a new terminal window
- Check if the command is found: which brew returns empty on failure
- Look for Homebrew in /usr/local/bin or /opt/homebrew
- Check your shell profile files for brew initialization block
Install Homebrew correctly
Install Homebrew using the official installation script from the Homebrew website. The command is: /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)". Paste this exactly as shown, including the quotes. The installer will prompt for your user password and explain what it will do before making any changes.
After installation, the script outputs specific instructions to add Homebrew to your PATH. On Apple Silicon, you need to add eval "$(/opt/homebrew/bin/brew shellenv)" to your ~/.zprofile. On Intel, add eval "$(/usr/local/bin/brew shellenv)" to ~/.zprofile. Run the eval command directly in your current terminal to activate it immediately.
Once brew is in your PATH, verify with brew --version. The output should show the Homebrew version and a Git revision. If it prints a Ruby warning about bundler, you can safely ignore it — it does not affect OpenClaw installation.
- Apple Silicon: /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
- Intel: Same command works, just ensure Rosetta 2 is installed
- After install, follow the post-installation instructions to add brew to your PATH
- Verify: brew --version should print the version without errors
Use the alternative non-brew installation path
If Homebrew installation fails repeatedly or you prefer not to use it, the official macOS .pkg installer is the recommended alternative. It packages the OpenClaw runtime, relay extension, and CLI tool in a single installer that places files in /Applications/ClawMesh and /usr/local/bin without any dependency on Homebrew.
Download the installer from your ClawMesh dashboard under Downloads > macOS Installer. Double-click the .pkg file to launch the installer. The installation requires an administrator password because it installs a launch agent for automatic startup and a kernel extension for the relay driver.
After installation via the .pkg, verify everything is working by opening a new terminal and running clawmesh doctor. All checks should pass, including the relay connectivity test. If any check fails, the installer logs are available at /var/log/clawmesh-install.log for diagnosis.
- Download the official macOS .pkg installer from the ClawMesh dashboard
- Run the installer with Administrator privileges
- The installer does not require Homebrew or any other dependencies
- Verify installation with clawmesh doctor after completion
Configure OpenClaw after Homebrew installation
If you successfully installed Homebrew and want to use the brew installation path for OpenClaw, run brew install clawmesh/tap/clawmesh. This formula adds the ClawMesh tap to your Homebrew installation and builds the OpenClaw runtime from source. Build times vary but typically complete in under five minutes on modern hardware.
After brew installation completes, initialize the OpenClaw service with clawmesh service install. This registers a launchd agent that starts OpenClaw automatically on login and restarts it after any crash. Check the service status with clawmesh service status.
The brew path and the .pkg installer path install to different locations and maintain separate configuration files. You cannot use both simultaneously without one overwriting the other. Choose one path and stick with it.
- Run brew install clawmesh/tap/clawmesh after Homebrew is working
- Run clawmesh doctor to validate the CLI and runtime
- Sign in with clawmesh login and your workspace credentials
- Start the relay with clawmesh relay start
Get Started
Finish setup fast
Use the deployment path that avoids repeated dependency blockers.
Related pages
FAQ
Is Homebrew always required for OpenClaw on macOS?
No. The official .pkg installer does not require Homebrew at all. Use brew only if you prefer managing development tools through Homebrew.
Can I have both Homebrew and the .pkg installer?
Only one runtime can be active at a time. Both can be installed on the same machine, but you must use one or the other for active OpenClaw operation.
Does the .pkg installer work on Intel Macs?
Yes, the .pkg installer supports both Apple Silicon and Intel Macs. Download the correct architecture variant from your dashboard.
How do I uninstall Homebrew OpenClaw cleanly?
Run brew uninstall clawmesh/tap/clawmesh and brew untap clawmesh/tap. This removes the formula and tap but leaves your workspace configuration intact.