How to Install OpenClaw on Mac (Menu Bar App or Terminal, Step by Step)

Written by

You keep hearing people talk about OpenClaw, and you want it on your Mac tonight. Then the docs show you a menu bar app, a Terminal command, npm and a word called Gateway. Which one is yours? And what if your Mac is a few years old?

Here is the short answer. If your Mac runs macOS Tahoe 26.2 or newer, the easiest way to install OpenClaw on a Mac is the menu bar app: download the DMG from the OpenClaw releases page, drag OpenClaw into Applications, open it, choose This Mac, and let it set itself up. No Terminal, no Homebrew, no admin rights for that part. On an older Mac, or if you like the terminal, one command does the job: curl -fsSL https://openclaw.ai/install.sh | bash. Either way you need a way into an AI model: an existing Codex or Claude login, or an API key. The docs talk about a first chat in minutes; give yourself 20 so you can read along calmly. The steps for both routes are below.

Want one practical AI lesson like this every week?

No password needed – your reset opens instantly.

No password. Just your email, and you’re in.

Before you start: two things to check on your Mac

Open the Apple menu in the top-left corner and choose About This Mac. That one window answers both questions.

Your macOS version. The window shows the name and version number (Apple: which macOS is your Mac using). The OpenClaw app needs macOS 26.2 (Tahoe) or later. The Terminal route is more forgiving: the Node versions OpenClaw runs on are built for macOS 13.5 or later, and older releases “may still run them but are not supported” (OpenClaw docs: macOS app).
Your chip. If you see Chip followed by a name like M1 or M3, you have Apple silicon. If you see Processor with an Intel name, you have an Intel Mac (Apple: Mac computers with Apple silicon). OpenClaw has a download for each, plus a Universal one if you are not sure.

One more thing: access to an AI model. OpenClaw itself is free and open source under the MIT licence. The model behind it is what does the thinking, and that is what you pay for. Setup can reuse a Codex or Claude login you already have, or an OpenAI or Anthropic API key.

Still deciding whether OpenClaw is the right tool at all? Read OpenClaw vs Claude Code or OpenClaw vs Claude Cowork first. This page assumes you have decided.

Which install route fits your Mac?

The menu bar app (OpenClaw.app). A normal Mac app with a menu bar icon, a dashboard, a chat window and a Quick Chat bar. It carries its own runtime, so it needs no separate Node install. Best if you are on macOS 26.2 or later and would rather not touch Terminal.
The Terminal installer. One command that installs Node if needed, installs OpenClaw and starts a guided setup. Best for older Macs, or if you like to see what is happening.
npm. Only if you already manage Node yourself. Covered in one short block below.

A word you will see everywhere: the Gateway. That is the part of OpenClaw that runs in the background, holds your settings and connects your chat apps to the AI. Both routes end with a Gateway running on your Mac.

How to install OpenClaw on Mac with the menu bar app

Download the right DMG. Go to the OpenClaw releases page on GitHub and pick the Apple Silicon, Intel or Universal DMG. When this page was written, the docs pointed to release 2026.10.3. The docs also warn that some releases ship only CLI or Windows files; if the newest one has no Mac app, take the newest release that does.
Put it in Applications. Open the DMG and drag OpenClaw into your Applications folder. Do not run it from Downloads or from the disk image. The permissions page explains why: macOS ties permissions to the app’s path, and a release app should run from /Applications/OpenClaw.app so your grants stick (OpenClaw docs: macOS permissions).
Open it and approve two prompts. macOS asks if you want to open an app you downloaded: click Open. Then it asks if OpenClaw may find devices on your local network: click Allow. The app uses that to reach a Gateway on another machine (OpenClaw docs: Onboarding for the macOS app).
Read the security notice. It explains that OpenClaw is a personal agent for one trusted person by default. Continue when that fits you.
Choose This Mac. A window called Getting things ready prepares the included runtime, starts the Gateway and checks it. The docs say this step needs no runtime download, Node, Terminal, Homebrew or administrator access. Connecting an AI provider can still need internet (OpenClaw docs: Gateway on macOS).
Let it connect your AI. The app tries, in order: saved OpenClaw sign-ins, a Codex login, a Claude CLI login, an OPENAI_API_KEY or ANTHROPIC_API_KEY, and models already loaded in Ollama, LM Studio or llama.cpp. It tests each with a real request and keeps the first that works. If nothing works, it sets up the official Codex plugin and offers a ChatGPT sign-in. The dashboard shows what it picked, and you can switch.
Finish in the dashboard. A guided conversation helps with the rest: memory import, chat channels and permissions. All of it is optional, and you can come back to it later.

One setting to know on day one. On a fresh setup, the app runs the Gateway itself, so it stops when you quit the app. If you want OpenClaw to keep working with the app closed, turn on Keep OpenClaw running when the app is closed, next to Launch at login in the dashboard’s device settings. It is off by default. And try Quick Chat: press Option-Space for a Spotlight-style chat bar without opening a full window.

Install OpenClaw on Mac with Terminal

On an older Mac, or if you just prefer it: press Command-Space, type Terminal and press Return. Then paste:

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

The script checks your Node version and installs Node 26 through Homebrew if it is missing. It installs Homebrew only when it needs it for Node or Git (OpenClaw docs: Installer internals). Then it installs OpenClaw and starts the setup wizard. Next:

Pick Quick start. It finds an existing Codex or Claude Code login or API key, tests it with a real request, saves your settings and opens the web dashboard (OpenClaw docs: Getting started).
Make it run in the background. Quick start keeps the Gateway running in that Terminal window. Press Control-C to stop it, then run openclaw gateway install. On a Mac this creates a LaunchAgent, so the Gateway starts at login and restarts if it crashes. Your settings stay saved.
Check it:

openclaw --version
openclaw doctor
openclaw gateway status

The status should show the Gateway listening on port 18789. Then run openclaw dashboard to open the Control UI in your browser. If it loads, everything works.

Already manage Node yourself? The docs give this route for npm 12 or 11.16 and newer (on npm 11.15 or older, leave out --allow-scripts=openclaw):

npm install -g openclaw@latest --allow-scripts=openclaw
openclaw onboard --install-daemon

OpenClaw needs Node 24.16+ or 26.1+, and Node 26 is the recommended one (OpenClaw docs: Install).

Mac permissions, without the confusion

This is where most Mac installs get messy, so take two minutes here. macOS guards your screen, microphone, files and keyboard control behind separate permissions. OpenClaw asks only when a tool needs one: you see a Grant card in the chat, and the agent waits for you before it tries again.

Grant what you use, not everything. You will find the full list under Dashboard > Settings > This Mac > Permissions: Automation, Notifications, Accessibility, Screen Recording, Microphone, Speech Recognition, Camera and Location. For chat-based writing and research, you can leave the heavy ones off until a tool asks.
Screen Recording still says missing? Click Grant, switch on OpenClaw under Privacy & Security > Screen & System Audio Recording in System Settings, then quit and reopen OpenClaw.
Never give Accessibility to “node”. The docs warn that a node entry with Accessibility lets any script run through that Node control your Mac’s interface. Give it to OpenClaw.app instead, and remove a node entry if you added one by accident.
Files on your Desktop or in Documents hang? macOS may block background processes from those folders. The docs’ simple fix: put the files you want OpenClaw to work on in its own workspace folder, ~/.openclaw/workspace.

And one storage tip: keep OpenClaw’s data on your Mac’s own disk, not in iCloud Drive or another synced folder. The docs say sync delays and file locks can break sessions and credentials, and openclaw doctor warns you if your data sits in a synced folder.

Your first 15 minutes after the install

An install is only worth something once it does a job. Do these three things right away:

Send a first message. Something small and real: “Turn these notes into a checklist for tomorrow morning: [paste]”. If you get an answer, the AI connection works.
Connect Telegram if you want to message it from your phone. The docs call it the fastest channel to set up, since it needs just a bot token. By default, anyone new who messages your bot gets an 8-character pairing code, and nothing they send is processed until you approve it. Codes expire after one hour (OpenClaw docs: Pairing).
Run the security check: openclaw security audit. It tells you if your setup has drifted from the safe defaults (OpenClaw docs: Security). Fix what it flags before you add more channels.

Then give it one job you repeat every week, like a Friday summary of your notes file. If you would rather build agents with drag-and-drop tools, see how to build an AI agent without code.

Can you run the AI model on your Mac too?

Yes, but go in with open eyes. If you already have a model loaded in Ollama, LM Studio or llama.cpp, the app’s setup can find it, and the docs say it never downloads a model by itself. For a guided route, install the llama.cpp plugin, run openclaw onboard and choose Managed local server. It shows the model, download size and backend before downloading, and tests a real tool call before making it your default. The smallest recipe needs at least 8 GiB of memory, and larger ones need more (OpenClaw docs: Local models). The same page is honest about the catch: local models do not have the safety filters of hosted providers. Start with a hosted model, get one real task working, then experiment.

Planning to buy a Mac just for this? See which Mac mini specs OpenClaw actually needs, for a cloud model and for a local one.

When the install does not work

Not sure what is wrong: run openclaw triage. It runs read-only checks and writes a clean description of the problem, and can hand it to Claude Code, Codex or OpenClaw’s own agent. The docs say nothing leaves your Mac until you choose one.
“command not found: openclaw”: close Terminal and open a new window first. If you used the app, check that it runs from Applications: the docs say copies running from Downloads, the Desktop or a disk image do not add the openclaw command to your shell. On the Terminal route it is almost always a PATH problem, and the Node.js page in the docs walks you through it.
The app’s setup fails: choose Retry setup. You can also open Connection… from the menu bar icon, where the app offers Install, Update or Repair Gateway. If the app says its runtime is missing or broken, reinstall OpenClaw.app.
A permission prompt never shows up: quit the app, remove OpenClaw under System Settings > Privacy & Security, open it again from Applications and grant again. The docs add that some permissions only come back after a full restart.
The Gateway keeps restarting: run openclaw gateway status and openclaw doctor. The log lives at ~/Library/Logs/openclaw/gateway.log.

Should you put it on your work Mac?

Ask first. OpenClaw runs in the background, can be reached from chat apps, and can be given tools that act on your Mac. The setup’s own security notice says it is built for one trusted person, and shared setups need extra lock-down. On a company laptop, that is a conversation for your IT team. A personal Mac is the easier place to learn.

Wondering whether a desktop agent that clicks through your apps fits your office better? Our guide to the best AI agent for desktop workflows compares the options. Setting it up on a PC too? Here is how to install OpenClaw on Windows.

Quick answers

Does OpenClaw work on an older Mac?

The menu bar app needs macOS 26.2 or later. The Terminal install runs on Node, whose Mac builds are made for macOS 13.5 and later. Older versions may work but are not supported.

Apple silicon or Intel?

Both. There is a separate DMG for each, and a Universal DMG if you are not sure which you have.

Do I need Homebrew?

Not for the app. The Terminal installer uses Homebrew only if it needs it to install Node or Git.

Is OpenClaw free?

The software is free and open source (MIT licence). You pay for the AI model you connect, unless you run a local model on your own Mac.

How do I uninstall it?

Preview first with openclaw uninstall --dry-run --all, then run openclaw uninstall --all to remove the service, settings, workspace and app. Want to keep your agent’s files? Run plain openclaw uninstall and pick what to remove. If you installed the app, also delete it from Applications (OpenClaw docs: Uninstall).

Check your macOS version, pick your route, and send your first message before you close the lid tonight.

Want the next one in your inbox?