AI
OpenClaw arrives on iPhone and Android
OpenClaw’s new iPhone and Android apps connect to a remote gateway and add voice, photos, calendar, contacts, and Android notifications.
OpenClaw now has official companion apps for iPhone and Android, but the mobile release is not a self-contained agent. According to Tom’s Guide, the apps connect to an OpenClaw gateway running on a separate computer or server that must remain powered on and reachable.
The apps give OpenClaw a direct mobile interface instead of requiring users to communicate through Discord, Slack, or Telegram. They also expose phone-specific inputs, including voice notes, photos, contacts, calendar data, and location. Android adds notification forwarding, allowing the agent to receive live updates about activity on the phone.
That makes the release more significant than a conventional chatbot app, but it also preserves OpenClaw’s existing architecture: the phone is a remote control and sensor, while the actual gateway remains elsewhere.
OpenClaw mobile setup requires a separate gateway
New users must first install and configure OpenClaw on a desktop or server. The mobile app then pairs with that existing agent, typically by scanning a QR code generated by the gateway and confirming the required credentials.
Users who have lost their gateway token can open the OpenClaw command-line interface and run:
''text openclaw dashboard --no-open ''
Once pairing is complete, the app presents a permissions screen. The permissions determine which tasks the agent can perform and what information it can access, so the mobile setup is also an access-control decision rather than just a login step.
After approving permissions, users can tap Go to chat and send a message. A response confirms that the basic connection between the smartphone and the remote gateway is working.
Camera, microphone, calendar, and notifications
The phone becomes useful as an always-available input device. Users can tap the microphone button to send a voice note or use the plus button to attach a photo, making it possible to capture ideas, images, or instructions without returning to a computer.
The iPhone app also includes an experimental voice-wake feature intended to activate OpenClaw after a chosen wake phrase. Tom’s Guide’s writer said the feature did not work during testing, leaving an important part of the hands-free experience unproven.
OpenClaw can also answer questions using information from the phone’s calendar and contacts. Access is enabled through Settings > Permissions, followed by the privacy and access controls. The calendar integration reads information already available on the phone; it does not separately sign in to a Google or Microsoft account.
Android users can additionally enable notification forwarding. That feature sends live phone notifications to the OpenClaw agent, potentially giving it a broader view of what is happening on the device than the iPhone app currently offers.
Permissions are the real trade-off
The mobile apps remove friction from using OpenClaw away from a desk, but they also make the agent easier to connect to sensitive personal data. Contacts, calendar entries, location, photos, voice recordings, and—in the case of Android—notifications can all become part of the agent’s operating context if users approve access.
That matters because OpenClaw has already been associated with autonomous actions that can affect other people. In our previous coverage of an OpenClaw gym reservation hack, an agent using Claude exploited a gym API, canceled another customer’s reservation, and exposed the risks of giving autonomous software broad authority. The mobile app does not create that underlying risk, but it makes granting an agent access to more personal and real-world inputs considerably easier.
Tom’s Guide’s walkthrough focuses on setup and capabilities, while the reporting does not establish the apps' pricing, supported gateway hosting options, or a detailed security model for transmitting mobile data. It also does not say when the voice-wake feature will become reliable or whether feature parity between iPhone and Android is planned.
Our read is that the apps are a meaningful usability upgrade, not a replacement for the computer or server running OpenClaw. They make the agent more available—and therefore potentially more useful—but the permission model deserves as much attention as the chat interface. Until the security controls and mobile data handling are clearer, the sensible position is to start with the narrowest permissions possible rather than treat the companion app as a harmless messaging client.