Deploy Openclaw on iOS
Quick Start
Running Openclaw on iOS requires pairing your iPhone or iPad with a Gateway running on a host machine. This guide walks you through the complete setup process.
Prerequisites
- A macOS or Linux machine to run the Openclaw Gateway
- An iOS device (iPhone or iPad)
- Both devices on the same network (or connected via Tailscale)
Step 1: Start Your Gateway
Ensure your Openclaw Gateway is running on your main host machine. Start it in your terminal with:
openclaw gateway --port 18789 If your phone and Gateway are on different networks but connected via Tailscale VPN, ensure your Gateway is bound to the tailnet IP.
Step 2: Install the Openclaw iOS App
Download the Openclaw app from the App Store or TestFlight (depending on availability). Once installed, open the app and proceed to pairing.
Step 3: Pair Your Device
When you first open the iOS app, it will attempt to connect to your Gateway. You'll need to approve this connection.
Option A: Via the Gateway Terminal
On your Gateway host machine, list and approve the pending device:
openclaw devices list openclaw devices approve <requestId> Option B: Via Telegram (if configured)
If you use the device-pair plugin, you can pair directly from Telegram:
- Message your bot: /pair
- The bot will reply with a setup code
- In the iOS app Settings, paste the setup code to connect
- Back in Telegram, reply with /pair approve
Step 4: Configure Your Connection
Once paired, the iOS app will remember your Gateway settings. You can customize:
- Gateway URL and port
- Auto-reconnect behavior
- Notification preferences
Troubleshooting
| Issue | Solution |
|---|---|
| Cannot find Gateway | Verify both devices are on the same network or Tailscale is connected |
| Pairing request not appearing | Run openclaw devices list manually on the Gateway host |
| Connection drops frequently | Check firewall settings and ensure port 18789 is open |
Best Practices
- Use a static IP or Tailscale for reliable connections
- Enable persistent notifications for important messages
- Consider running your Gateway on a VPS for 24/7 availability
For server deployment options, check out our guide on VPS Hosting.
