🦞AIClawGuide
Community Guide

OpenClaw App

What people usually mean by the OpenClaw app, covering the macOS companion app, iOS and Android node apps, and the current Windows status.

Mar 19, 2026

Does OpenClaw have an app?

Yes, but not in the “one universal app on every platform” sense that many people expect.

Today, the OpenClaw product surface is split across:

  • a macOS companion app
  • an iOS node app
  • an Android node app
  • a Windows path that is still WSL2-first, not a native companion app

That is why searches for openclaw app often feel confusing. People are using one phrase for several different product surfaces.

The most complete app experience today is on macOS

The official docs describe the macOS app as the menu-bar companion for OpenClaw.

It can:

  • manage or attach to the local Gateway
  • own macOS permissions such as notifications, accessibility, microphone, and screen recording
  • expose macOS-only node capabilities
  • provide a more native operator experience around Gateway lifecycle and device features

In practice, this is the closest thing OpenClaw has to a traditional desktop companion app.

iPhone and Android are node apps, not full local Gateway hosts

The current iOS and Android apps are better understood as node apps than as “install one app and everything runs there” products.

The docs describe them as device-side clients that connect to a Gateway running somewhere else.

That means:

  • they depend on another machine for the Gateway
  • they expose device capabilities back to the OpenClaw system
  • they are part of the product, but not the whole runtime

This distinction matters because a lot of user confusion comes from expecting the mobile app to behave like the entire platform.

What the macOS app actually adds

The macOS app is not just a wrapper around the browser UI. According to the official platform docs, it acts as a broker between the local machine, TCC permissions, and the Gateway.

Key practical functions include:

  • menu-bar status and notifications
  • local-versus-remote Gateway handling
  • node capabilities such as Canvas, camera, screen recording, and system.run
  • a more native operator workflow on macOS

If you want the richest “OpenClaw app” experience today, macOS is where it exists.

What the iOS app actually is

The iOS app is currently framed as an internal-preview node app.

It connects to a Gateway over:

  • LAN discovery
  • tailnet / DNS-SD
  • manual host and port

It can expose device-facing features such as:

  • canvas
  • camera
  • screen snapshot
  • location
  • talk mode
  • voice wake

That makes it useful, but it is still a companion to a Gateway, not a replacement for one.

What the Android app actually is

The Android app is also a node-oriented app rather than a standalone Gateway host.

The official docs describe it as a companion node app with:

  • gateway connection and pairing
  • chat and history access
  • voice and canvas surfaces
  • Android device commands such as notifications, location, photos, and contacts

So when someone asks “Is there an OpenClaw Android app?”, the answer is yes. But the precise answer is “yes, as a node app that works with an existing Gateway.”

What about Windows?

Windows is the clearest place where the phrase openclaw app can mislead people.

The official docs currently recommend WSL2 for Windows. Native Windows companion apps are planned, but the supported path today is still:

  • run the CLI and Gateway in WSL2
  • treat Windows as a host for the Linux runtime

So if the real question is “Can I install a native OpenClaw Windows app like a normal desktop client?”, the current answer is effectively no.

The right mental model

The cleanest way to think about the product today is:

  • Gateway is the control plane
  • macOS app is the richest desktop companion
  • iOS and Android apps are node apps
  • Windows is supported through WSL2, not a mature native companion app

That matches the official README and platform docs much better than the idea of one identical app everywhere.

FAQ

Is there an OpenClaw app for Mac?

Yes. The macOS companion app is the most complete native app surface in the current platform lineup.

Is there an OpenClaw app for iPhone?

Yes, but it is currently described as an iOS node app that connects to a Gateway running elsewhere.

Is there an OpenClaw app for Android?

Yes. Android has a node app that connects to a Gateway and exposes device-side capabilities.

Is there a native Windows OpenClaw app?

Not as the main supported path today. The official recommendation is still Windows via WSL2.

Where to go next