OpenClaw merged PR #99767, "feat(macos): install and run the local Gateway automatically" early on July 4th, bringing the Mac app closer to a true first-run installer.
The problem was straightforward: people could download OpenClaw for Mac and still fail to complete setup from the app alone if the CLI, Node.js, and local Gateway were not already present. That is a big onboarding gap for a desktop app whose best experience should start inside the app, not in a terminal checklist.
The PR also fixes a smaller but important trust-flow annoyance. Fresh local installs could prompt for approval of the Mac app's own node, even though that node belongs to the local setup path the user just chose.
What Changed
The Mac app now bundles the canonical CLI installer, defaults onboarding to This Mac, installs and starts the local Gateway, and waits until the Gateway is ready. A new user should be able to drag OpenClaw into Applications, open it, choose the recommended local setup, and reach a working agent.
The local node pairing flow is also tighter. Fresh installs use a dedicated node identity, and the app silently approves only the exact persisted node identity in local mode. Remote nodes and mismatched identities still require explicit approval.
That distinction matters. The change removes an unnecessary prompt for the app's own local node while preserving the approval boundary for anything that is not the expected local identity.
Why It Matters
Mac onboarding is often the first impression for users who want OpenClaw as a personal agent, not just as a developer project. If the first-run path depends on preinstalled runtime pieces, the desktop app feels more like a wrapper than a complete product.
PR #99767 moves more of that responsibility into the app:
- CLI installation is part of the onboarding flow.
- The local Gateway starts automatically.
- The app waits for Gateway readiness before moving on.
- The local Mac node can be approved without a redundant pairing sheet.
That should reduce the number of users who stall before they ever reach a live conversation.
Validation
The PR says the flow was tested from a fresh Parallels macOS Tahoe 26.5 snapshot where OpenClaw, its state, the CLI, and Node.js were absent. The final signed and notarized universal DMG passed hdiutil verify, stapler validate, and Gatekeeper assessment.
In the clean setup proof, OpenClaw installed CLI/Gateway 2026.6.11, loaded the LaunchAgent, reached the loopback Gateway at 127.0.0.1:18789, and completed onboarding. The app's own node reported approved, paired, and connected, with no node approval sheet shown during setup.
The PR also reports a live OpenAI-backed onboarding turn that returned the exact response OPENCLAW_E2E_OK, plus focused Swift, macOS onboarding, installer, package, and JavaScript build validation.
Bottom Line
This is a meaningful platform improvement for OpenClaw on macOS. The app can now carry more of the setup burden itself, while keeping remote and mismatched node approvals explicit.
For first-time Mac users, that makes OpenClaw feel less like a multi-step system install and more like a desktop app that knows how to bring its agent runtime online.