
A SAGE9AI beginner install guide for the current native-app path: download OpenClaw.app, choose This Mac, connect one AI provider, pass the live model check, and open the dashboard.
Goal: install the official OpenClaw macOS app, let it create a local Gateway on This Mac, verify one AI connection, and send one safe test message.
The current official macOS path supports complete first-run setup inside OpenClaw.app. The app installs its matching external CLI runtime, starts a local Gateway, tests the AI connection you select, and then opens the dashboard.
OpenClaw.app from the official GitHub release assets.
The browser dashboard opens and one safe message gets an AI reply.
Source builds, optional chat channels, hooks, webhooks, remote hosting, and deep customization.
Confirm these basics before installing:
| Path | Use when | Beginner note |
|---|---|---|
| OpenClaw.app | Your Mac runs macOS 15+ and you want the easiest visual setup. | Use this guide. Download the .dmg from official releases. |
| CLI installer | You only need the CLI/Gateway, use an older supported macOS for Node, or support asks for Terminal setup. | Valid alternative. It launches CLI onboarding and the browser dashboard. |
| Source build | You are contributing or support specifically asks for it. | Not a beginner path. |
Use only the official OpenClaw GitHub release assets. The preferred Mac download is OpenClaw-<version>.dmg.
Use the newest release that does include a .dmg or .zip. Do not download look-alike installers from third-party sites.
OpenClaw.app now handles the beginner setup sequence. Make each choice explicitly; detection never authorizes or selects a provider for you.
| If OpenClaw asks... | Beginner answer | What happens |
|---|---|---|
| Where to connect | Choose This Mac. | The app installs its matching external CLI runtime and starts a local Gateway. Choose an existing Gateway only if you already operate one. |
| AI connection | Select one provider or existing connection you recognize. | OpenClaw tests only the connection you explicitly select. |
| Login, OAuth, device code, or API key | Follow the official provider flow. Never share a code or key, and continue only if you initiated it. | The selected provider is authorized for OpenClaw. |
| Live model check | Wait for it to pass. Retry or choose another connection if it fails. | A real completion proves the AI route can answer before setup finishes. |
| Memory, channels, or permissions | Finish basic setup first. Grant only the Mac permissions you understand. | The dashboard can guide these later; permissions remain available under Settings → This Mac → Permissions. |
After the live model check succeeds, the app opens the dashboard. Confirm the local Gateway is connected and send one safe message. The commands below are optional checks for users who also use Terminal:
You want to see the Gateway running, usually on port 18789.
This opens the browser dashboard. If it loads, you are in the main OpenClaw interface.
The main chat is the normal dashboard chat area. Type a safe test message such as:
If you get a useful reply, the first install goal is complete.
The Gateway is the communication hub. OpenClaw’s docs say gateway auth uses a token by default. Treat any gateway token, remote token, API key, or password-like value as private.
OpenClaw can connect to many channels, but a complete beginner should not configure all of them during first install. Add one channel only after the dashboard chat works.
| Channel choice | Beginner guidance |
|---|---|
| Dashboard / WebChat | Use this first. It is already connected through the local Gateway and proves the core setup works. |
| Telegram | Optional later. It requires a bot token and an allowlist/pairing step. |
| WhatsApp, Signal, Slack, Discord, iMessage, Teams, Google Chat | Useful later. Each has its own setup, account, pairing, permissions, and troubleshooting path. |
| Group chats or ambient rooms | Skip until you understand mention behavior, allowlists, and bot-loop protection. |
Use this only when you want a terminal-first installation, only need the CLI/Gateway, or cannot run OpenClaw.app. The hosted installer detects the OS, provisions a supported Node runtime when needed, installs OpenClaw, and launches onboarding.
| Problem | First fix |
|---|---|
| The Mac app will not install or open. | Confirm macOS 15+ and verify the download came from official releases. If the newest release lacks a Mac asset, use the newest one that includes a .dmg or .zip. |
openclaw: command not found | Quit and reopen Terminal, then try again. If it still fails, rerun the official installer or check the OpenClaw install docs. |
| OpenClaw opens but does not answer. | Return to model/provider setup. The first chat requires a provider that passes the live model check. |
| The dashboard does not open. | Run openclaw gateway status. If the Gateway is not running, use openclaw doctor or rerun onboarding. |
| Channel setup is confusing. | Skip channels until dashboard chat works. Add one channel later, starting with Telegram if it fits your needs. |
| The macOS app asks about local vs remote Gateway. | Choose This Mac for a normal personal Mac setup. Remote is for advanced multi-machine setups. |
Once OpenClaw answers in the dashboard, use one simple workflow first. Do not customize every channel or automation before the first practical win.
Once your basic agent is up and running, it can install, configure, and set up anything else you would like within the agent harness. No need to guess or research how to do it, because your agent already knows. Just ask it. For safety, tell it to explain the plan before making changes, connecting accounts, or sending messages.
Official sources checked: macOS, Install, Onboarding Wizard, and GitHub Releases. Key facts: OpenClaw.app requires macOS 15+; .dmg is preferred; This Mac installs a matching external CLI runtime and starts the local Gateway; the user explicitly selects an AI connection; a live model check must pass before the dashboard opens.