OpenClaw released companion native apps for iOS devices. Android. The iOS app is listed as ‘OpenClaw – AI that does things.’ Download both apps for free. These aren’t standalone chatbots. Every phone is a node of a network that hosts its own agents. The assistant runs separately on its own Gateway. The whole concept is based around this separation.
TL;DR
- OpenClaw iOS apps and Android app are companion nodes. They’re not stand-alone assistants.
- Gateway is the main agent, while phones can add location, audio, Canvas, and camera.
- The port number 18789 is used to pair nodes over WebSocket.
- Keep privacy-sensitive commands off the list until you have allowed them.
- You will need a Gateway for macOS, Linux or Windows (WSL2)
OpenClaw?
OpenClaw AI is an open-source AI personal assistant/agent. Peter Steinberger, with the help of community contributors, created OpenClaw. This project is an independent one and has no affiliation with Anthropic. TypeScript is used to write the core. Node 24 or Node 22,19+ is the recommended runtime. It runs on macOS or Windows using WSL2. It can be accessed through chat applications you are already using. Channels supported include WhatsApp, Telegram Discord Slack Signal and iMessage. The agent is able to browse the internet, execute shell commands and read/write files. This model can work with any type of hosted, subscription, gateway, local or local model. Your chosen API key. It supports persistent memory as well as community plugins.
The Gateway-and-Nodes Architecture?
Gateway is a single-plane control. Session, routing, channel, tools and events are all owned by the Gateway. One Gateway is run on each machine. The Gateway is the only place where chat messages are delivered. A node connects to the Gateway. Nodes communicate over WebSockets on port 18789. The node must be registered. role: "node" during pairing. The nodes reveal a surface of command through node.invoke. The command families are canvas.*, camera.*, device.*, notifications.*” system.*. Documentation is clear: “Nodes are peripherals and not gateways.” Apps discover the Gateway on a local network via mDNS/Bonjour. OpenClaw suggests Tailscale for remote access. wss:// endpoint.
Why do Mobile Apps add value??
It gives an agent a physical body. Your workflows will be able to use device-specific hardware. It pairs with iOS apps via QR code or set-up code. Chat, background Talk and realtime talk mode are supported. OpenClaw allows you to share media, text and links from iOS. Camera, screen, GPS, photo, contact, calendar and reminders are all optional capabilities. Android is not an independent gateway, but a companion app. The app offers live chat responses, attachments of images, and a full history of sessions. Talk Mode is available with ElevenLabs TTS or the system. Agents can render dashboards, tools and other information on a live canvas surface. Android gives permissions to each app individually. Gateway connections are kept active by the foreground services.
iOS Node vs Android Node
| Capability | iOS — OpenClaw – AI that does things | Android — OpenClaw’ node |
|---|---|---|
| Role | Companion Node | Companion Node |
| Pairing | QR code is also known as a setup code | Host/port setup code or manually operated host/port |
| Chat | Use the iPhone to chat | Your full session history includes image attachments as well as a stream of replies. |
| Vocalists | Both Realtime Talk and Background Talk Mode | Talk mode (ElevenLabs system TTS or talk mode) |
| Canvas | Canvas surface | Live Canvas surface |
| Device capability | Camera, screen, location, photos, contacts, calendar, reminders | Location, cameras, photo, screen captures, notifications, calendar, SMS and motion sensors |
| Take action. | Reviewed from iPhone | Managed on the Gateway |
| Data collection | None declared (App Store) | None declared (Google Play) |
| The Requirement | iOS 18.0+, and running Gateway | The Gateway running on macOS, Linux or Windows |
Use Cases with Examples
Imagine collecting data on the jobsite. Photographing conditions is done by the agent using iOS. GPS coordinates for each image are used to tag the location. Consider a context-aware reminder. An agent initiates a job when you enter a location. Take an Android notification. Agent reads the notification and composes a response. Consider a live dashboard. An agent will push a Canvas screen onto your monitor. You can use the device without using your hands. Talk Mode maintains a voice conversation. There is a caveat for screen-capture and the camera. Apps must be running in the front-end. The background calls will return an error.
The Minimal Guide to Pairing Your Phone
Run the Gateway first on an supported host.
# on the Gateway host, either MacOS, Linux or Windows (via WSL2)
Install openclaw using npm -g the latest version.
Openclaw onboard --install daemon
Open the app, and then select one of your discovered Gateways. Enter the port and host manually. App connects to role: "node" It sends an device pairing. The Gateway CLI will allow you to approve the request.
Openclaw Devices List
Approval of open-claw devices
Openclaw Nodes Status # Confirm the node has been paired with a connected node
By default, privacy-sensitive commands are turned off. Examples include camera.snap, camera.clip” screen.record. You can opt out explicitly by clicking on gateway.nodes.allowCommands You can configure your system to suit you.
// ~/.openclaw/openclaw.json
{
gateway: {
nodes: {
allowCommands: ["camera.snap", "screen.record"],
},
},
}
A deny list (gateway.nodes.denyCommandsThe list of allowed items always loses out to the list.
Safety and Approvals
Devices store pairing credentials. Each node must receive approval from the Gateway before it can be connected. The durable role contract is the device pairing record. The token rotation can’t upgrade a node to a new role. Screen capture and camera are restricted by permission and only run in the background. Cleartext ws:// This is only available on LAN .local hosts. Endpoints at public or tailscale require real hosts. wss:// TLS endpoint.
Click here to see the Interactive Explainer
Interactive Explainer
Explore the Gateway-and-Nodes architecture, simulate a chat command flowing to a phone’s hardware, and walk through device pairing — all in your browser.
Illustrative simulation · runs locally · no real Gateway is connected
① Architecture map
② Command-flow simulator
③ Pairing walkthrough
Gateway is your single source of Truth
To learn more about a block, click on it. Messages always land on the Gateway — never directly on a phone.
Chat Apps + Plugins
⬡ Gateway
sessions · routing · channels · events
Surfaces the Gateway drive
OpenClaw agent
tools · memory
CLI/Web UI
Control plane
iOS / Android nodes
role: “node”
⬡ Gateway
Single control plane It runs on macOS (WSL2), Linux or Windows. Sessions, routings, tools, events, and channels are its property. A single Gateway serves all channels and nodes at the same time.
Use a virtual command to reach your hardware
Choose a channel, and then perform the task. Watch requests flowing through the Gateway and to nodes’ node.invoke Command surface
Telegram
Discord
Photo the shelf I’m standing in front.
What am I doing right now?
Display a live dashboard in my cell phone
You can read my most recent notification and write a response
Choose the options and click Run.
Active hop
You can complete the form by clicking on this link.
requires foreground / opt-in
Pair a phone as a node
WebSockets on port are used to connect nodes. 18789 Each step requires explicit approval. Play to walk through the handshake.
1
Start the Gateway in a host
Run Openclaw onboard --install daemon On macOS, Linux (WSL2), or Windows.
2
App Discovers the Gateway
The app searches for it using mDNS/Bonjour on the same WiFI. Remote is a wss:// Endpoint of the tailscale
3
The phone sends an pairing request
Node connected to WebSocket role: "node" The device is identified.
4
The operator approves the Gateway
Openclaw Devices List → Approval of open-claw devices
5
Pairing and connecting the node
Openclaw Nodes Status The following is a list of the most recent shows. paired · connected. Keep privacy-sensitive commands off until they are listed.
Strengths and limits
Strengths:
- Local-first design allows you to keep all your keys, configuration, and data in the machine that you own.
- One Gateway can handle many channels, and multiple nodes simultaneously.
- The phone adds hardware such as camera, GPS, voice and Canvas.
- Both store listings report no data collection.
Limitations:
- To do anything, the mobile apps require a Gateway that is running.
- Tailscale, WebSockets, and mDNS are sometimes used to set up the setup.
- The app must be running in the foreground to capture screen shots and take pictures.
- Android’s listing indicates 10+ downloaded apps as an indication of a very early stage.
- The full system is very broad, and requires careful list of allow-listing.
Take a look at the Android Then, there is the iOS app. Also, feel free to follow us on Twitter Don’t forget about our 150k+ML SubReddit Subscribe now our Newsletter. Wait! What? now you can join us on telegram as well.
You can partner with us to promote your GitHub Repository OR Hugging Page OR New Product Launch OR Webinar, etc.? Connect with us

