OpenClaw just shipped official iOS and Android apps, ending months of users routing everything through Telegram or WhatsApp to talk to their agent on the go. I downloaded one of them within the hour. Then I sat there with an app open and nothing to connect it to, because I deleted my own OpenClaw instance back in May. That gap between downloading the app and actually using it turns out to be the whole story.

What actually launched

The OpenClaw Foundation, the non-profit that now stewards the project, announced the launch on June 29, and notably, Apple had long resisted letting agentic AI tools onto the App Store. The apps let you chat with your assistant, use real time voice, approve actions, and get push notifications, all from your phone instead of a messaging app standing in as the interface.

But the apps are not standalone AI. Each one acts as a “node” that pairs with an OpenClaw Gateway you run yourself, on a Mac, Linux box, or Windows PC, with the phone linking to it over your home network or a private tailnet, usually via a quick QR code scan. No gateway running somewhere, no functioning app. It’s a remote control, not the brain.

Once paired, both apps cover the same core ground. You can chat with your assistant, use real time Talk mode with push to talk support, review and approve actions requested by your Gateway, and receive push notifications and status updates for connected workflows. Talk mode is closer to a walkie talkie than a phone call. You hold to speak, the agent processes it, and every action it wants to take still waits for your approval before it runs. Nothing fires automatically just because you spoke to it.

The two platforms aren’t identical though. The iOS version additionally exposes access to photos, contacts, calendar, and reminders when the user opts in, and supports sharing directly into the assistant, while Android supports launching OpenClaw via the Google Assistant trigger, so holding the home button or saying “Hey Google, ask OpenClaw” routes directly into the app. So an iPhone user gets a slightly deeper hook into personal data sources, and an Android user gets a faster way in through the OS itself. Worth knowing before you grant anything, since the app can tap the camera, screen, microphone, location, photos, contacts, calendar, and reminders, and every gateway action waits for your approval first. The permission list looks broad on paper. In practice it’s opt in per capability, not all or nothing.

Launch day did not go smoothly

Initial reviews are mostly negative, with the app sitting at a 2.2 star rating and widespread reports of it being buggy, unable to pair, or simply not working once connected. Several users commenting on OpenClaw’s announcement said they couldn’t pair the app with their Gateway at all, while some who did manage to connect reported that “nothing works.”

Rough launches happen. What’s more interesting to me is what’s underneath the pairing complaints.

The part that trips people up: away from home means real setup

I tested the assumption that the app would just find your Gateway wherever you are. It won’t, not by default. The Gateway WebSocket binds to loopback by default, meaning for remote use you need to expose it through Tailscale Serve, a trusted LAN or Tailnet bind, or an SSH tunnel. Loopback means it only talks to the machine it’s running on. The moment you step outside your home WiFi, the phone has nothing to find.

Looking at the actual app, there are three connection paths, not one. Home Network covers LAN or a Tailscale host, which is the easy case when phone and gateway share a network. Remote Domain is built for a VPS with its own domain name, meaning you point a subdomain at your server, put HTTPS and a token in front of the Gateway, and the phone connects to that public address directly, no VPN app required. And for desktop clients specifically, an SSH tunnel works as the universal fallback when neither of those fits.

None of these are wrong choices. But none of them are “open app, scan QR, done” either, the moment you want access from a coffee shop instead of your living room. That’s a real setup step that a non technical person downloading from the App Store has no reason to expect.

Why this matters more for OpenClaw than most apps

This is the tradeoff baked into self hosting in general, not a OpenClaw specific failure. The Gateway runs on your own machine by default, reachable only from that machine, which means mobile access, webhook integrations, and remote companion app connections all require deliberately exposing it to the outside world. That’s the same privacy first design that makes OpenClaw appealing to people who don’t want their assistant’s data sitting on someone else’s cloud. The cost of that control is that you, not Apple or Google, are responsible for making the thing reachable.

I ran OpenClaw on a Hetzner VM for months before shutting it down in May for a different agent. I deleted it because Lollie had quietly become the agent I actually used. That reasoning hasn’t changed. But this mobile launch is a good enough reason to set OpenClaw up again, not as a daily driver, just to actually go through the Remote Domain setup, pair the app, and see whether the experience holds up once you’re past the App Store screenshots. I’ll document the whole thing, config included, so if you’re trying to figure out which of the three paths makes sense for your own setup, you’ll have a real walkthrough instead of guesswork.

FAQ

Do I need Tailscale to use the OpenClaw mobile app?
Not necessarily. Tailscale is one of three supported connection modes in the app, alongside a Home Network LAN setup and a Remote Domain option for VPS users with their own domain and TLS certificate. You need one of the three to use the app away from your home network.

Can I use the OpenClaw app without running my own server?
No. The app is a client only. It requires an OpenClaw Gateway running somewhere you control, there is no hosted version you can just log into.

What’s the difference between the iOS and Android OpenClaw apps?
They cover the same core features, chat, Talk mode, approvals, and notifications. iOS adds opt in access to photos, contacts, calendar, and reminders with direct sharing into the assistant. Android adds a Google Assistant trigger so you can launch OpenClaw hands free.

Is the OpenClaw app safe to use away from home?
It can be, but only if the Gateway is exposed properly. The documentation explicitly warns against exposing the gateway port publicly without TLS and authentication. A bare port forward with no token or certificate is not a safe setup for remote access