OpenClaw LaunchOpenClaw Launch
← Home

Guide

OpenClaw Android App

The official OpenClaw Android app turns your phone into an AI node — connecting your camera, microphone, screen, and sensors to a running OpenClaw gateway. It is a free download on Google Play; an official iOS version is available too, released on the App Store on June 24, 2026. This guide covers installation, connection methods, and how to use it with your OpenClaw Launch managed instance.

What Is the OpenClaw Android App?

The OpenClaw Android app is a companion / node app, not a standalone gateway. It connects to an existing OpenClaw gateway over WebSocket and exposes your Android device's hardware — camera, microphone, screen, and sensors — as tools the AI agent can use.

Think of it as extending your AI agent's reach into the physical world. Once connected, your agent can see through your phone's camera, hear through the microphone, speak aloud, and display content on your screen — all while the gateway handles the AI reasoning, model routing, and skill execution.

The app does not run an OpenClaw gateway itself. You still need a gateway running somewhere — either self-hosted on a server or managed by OpenClaw Launch.

What You Need

  • An OpenClaw gateway running somewhere — a self-hosted Docker instance, a local install, or an OpenClaw Launch managed instance
  • An Android device running Android 12 or later — the app's minSdk is 31
  • The OpenClaw Android app from Google Play or sideloaded via APK
  • Network connectivity between your phone and the gateway — same LAN, Tailscale, or a public URL

How to Install

From Google Play

Install OpenClaw on Google Play (package ai.openclaw.app) — the official app by the OpenClaw team. This is the recommended method: you get automatic updates and verified builds.

Sideload via APK

If you prefer to sideload, download the latest APK from the OpenClaw GitHub releases page. Enable “Install from unknown sources” in your Android settings, then open the APK to install.

Connecting to Your Gateway

The app supports three ways to discover and connect to an OpenClaw gateway. Choose the method that matches your setup.

All three methods need pairing approval. Android connects as a device node, so whichever method you use, the gateway holds the request until it is approved. On a self-hosted gateway you approve it yourself with openclaw devices approve <requestId>; on an OpenClaw Launch instance the dashboard's OpenClaw App modal does it for you. Cleartext ws:// is fine on a private LAN address, .local host or localhost; anything crossing networks needs TLS.

Method 1: mDNS / NSD (Same LAN)

If your phone and gateway are on the same local network (same Wi-Fi), the app can discover the gateway automatically via mDNS (also called NSD on Android).

  1. Open the OpenClaw app and go to the Connect tab.
  2. The app scans for OpenClaw gateways on the local network. Your gateway should appear in the list within a few seconds.
  3. Tap the gateway to connect. Enter the auth token if prompted.
Not seeing your gateway? Make sure both devices are on the same Wi-Fi network. Some routers block mDNS traffic between clients — try Method 3 (manual URL) instead.

Method 2: Tailscale

If you use Tailscale for networking, the app can connect to your gateway over the Tailscale mesh network, even when your phone is on a different network (e.g., cellular).

  1. Install and enable Tailscale on both your phone and the machine running the gateway.
  2. In the OpenClaw app, go to Connect and tap Manual.
  3. Expose the gateway over TLS with Tailscale Serve, then enter the resulting https:// / wss:// MagicDNS address.
  4. Enter the auth token and connect.
Raw tailnet IPs do not work. The upstream Android docs state that tailnet and public mobile pairing does not use raw tailnet IP ws:// endpoints — Android requires a secure endpoint, so use Tailscale Serve (or another wss:// URL). An address like http://100.x.y.z:18789 will not connect.

Method 3: Manual Gateway URL

For any gateway accessible via a URL — public domain, IP address, or tunneled connection — enter the address manually.

  1. In the OpenClaw app, go to Connect and tap Manual.
  2. Enter the full gateway URL, for example:
    • https://openclaw.yourdomain.com (reverse-proxied with HTTPS)
    • http://192.168.1.100:18789 (LAN IP)
    • https://your-instance.openclawlaunch.com (OpenClaw Launch)
  3. Enter the auth token when prompted and tap Connect.

Connecting to Your OpenClaw Launch Instance

If you're using OpenClaw Launch for managed hosting, here is how to connect the Android app to your instance:

  1. Find your instance URL and auth token. Go to your Dashboard page on OpenClaw Launch. Click on your instance to open its detail page. You'll see the Gateway URL and Auth Token listed there.
  2. Open the Android app and go to the Connect tab.
  3. Tap Manual and enter your instance's gateway URL (e.g., https://your-instance.openclawlaunch.com).
  4. Enter the auth token from your dashboard and tap Connect.
  5. The app shows “Connected”. Your phone is now a node attached to your managed instance.
No CLI approval on managed instances. Pairing still happens — but if you open Connect Platforms → OpenClaw App on the dashboard, that modal watches for your phone's pairing request and approves it for you, flipping to Connected on its own. The openclaw devices approve step below is for self-hosted gateways, where there is no dashboard to do it. Pending requests expire after about 5 minutes, so have the app ready before you open the modal.
OpenClaw Launch advantage: Your instance already has HTTPS, auth tokens, and networking configured. No need to set up reverse proxies, trustedProxies, or allowInsecureAuth — just paste the URL and token.

App Navigation

The app's shell navigation is Home, Chat and Settings, plus the Connect surface used for initial gateway setup and dedicated Gateway and Approvals screens.

Home

Device and connection overview — current gateway, session and node status.

Chat

A built-in chat interface for interacting with your AI agent directly from the app. Works just like the gateway web UI — send messages, receive responses, and view conversation history. Voice interaction lives here rather than in a separate tab.

Connect

Gateway discovery and pairing. Shows connection status and lets you switch between gateways.

Gateway

Gateway configuration, reached from Settings.

Approvals

Review and approve actions the agent asks permission for.

Settings

App configuration — gateway connection settings, notification preferences, permission management, and theme options.

Camera & Canvas

Two of the most powerful features of the Android app are camera access and canvas display:

  • Camera: The app requests camera permission on first use. Once granted, your AI agent can take a still (camera.snap, jpg) or record a short clip (camera.clip, mp4) — capture on request, not a continuous live video feed. This enables visual tasks — reading documents, identifying objects, navigating spaces, or any scenario where the agent needs to “see.”
  • Canvas: The agent can render visual output — charts, diagrams, images, or interactive elements — directly on your phone's screen. The canvas is an overlay the agent brings up when it needs to show something, not a separate tab. This turns your phone into a dynamic display controlled by the AI.

Limitations

The Android app is a powerful companion, but there are some things to keep in mind:

  • Foreground only for camera & canvas: Camera capture and canvas display require the app to be in the foreground. If you switch to another app, these features pause until you return.
  • Requires an active gateway: The app is a node, not a gateway. If your gateway goes offline, the app can't function independently. It will reconnect automatically when the gateway comes back.
  • Android is a node, not a gateway: You cannot run an OpenClaw gateway on the Android app. The app connects to a gateway — it doesn't become one.
  • Battery usage: Frequent camera capture or sustained voice use consumes more battery. Use Settings to manage power-intensive features.

Frequently Asked Questions

Can I use the Android app without a server?

No. The app is a companion that connects to a running OpenClaw gateway. You need a gateway running somewhere — on a local machine, a VPS, or a managed instance from OpenClaw Launch. The app does not include a gateway.

Does the app work over cellular data?

Yes, as long as your gateway is reachable from the internet. If your gateway is behind a firewall (LAN only), you'll need Tailscale or a reverse proxy to make it accessible. OpenClaw Launch instances are always publicly accessible over HTTPS.

Is there an iOS app?

Yes. OpenClaw released an official native iOS app for iPhone, iPad, and Apple Watch. See the OpenClaw on iPhone guide, or the cross-platform mobile app overview.

Can multiple phones connect to the same gateway?

Yes. Each phone connects as a separate node. The gateway manages all connected nodes and can route tasks to any of them.

Do I need to pair the app like Telegram or Discord?

Not DM pairing — but yes, the app does pair. Android connects to the gateway WebSocket as a device node (role: node), so after you enter the URL and token it raises a pairing request that has to be approved before the connection completes. Who approves it depends on where the gateway runs.

OpenClaw Launch managed instance: open Connect Platforms → OpenClaw App on the dashboard. That modal watches for the request and approves it for you — no CLI.

Self-hosted gateway: approve it yourself.

openclaw devices list
openclaw devices approve <requestId>

If the app sits there not connecting, an unapproved pairing request is the first thing to check.

Related Guides

Don't Have a Gateway Yet?

Deploy your OpenClaw AI agent in 30 seconds with managed hosting. Then connect the Android app — no server setup required.

Deploy with OpenClaw Launch