#Mobile MoltBot
1 messages ยท Page 1 of 1 (latest)
Yes, you can use Moltbot on mobile! But there's an important distinction:
The Gateway needs to run somewhere (macOS, Linux, or a VPS). The mobile apps (iOS/Android) act as companion nodes that connect to a Gateway, not host it themselves.
Your options for mobile use:
1๏ธโฃ VPS + Mobile Terminal (SSH)
Run the Gateway on a cheap VPS ($5/mo on Hetzner), then SSH from your mobile terminal (e.g., Termius, Prompt):
# From mobile terminal, tunnel to your VPS:
ssh -N -L 18789:127.0.0.1:18789 user@your-vps-ip
# Then open in mobile browser:
http://127.0.0.1:18789/
๐ Docs: Linux VPS quick path | Hetzner VPS guide
2๏ธโฃ Mobile App as a Node
Install the Android or iOS node app, pair it to your existing Gateway (running on your Mac or a VPS), and get canvas/camera/location features on mobile.
๐ Docs: Android node | iOS node
3๏ธโฃ Mobile Browser + Web UI
Once your Gateway is accessible (via VPS or tunnel), access the full web UI from any mobile browser โ no app needed.
TL;DR: You can't run the full Gateway directly on mobile alone. Pair it with a VPS (Linux) and use your mobile as a terminal or node companion. The Linux VPS docs above have the exact steps! ๐ฆ
@primal path is it safer running it on VPS so bot is sandboxed?
Yes, absolutely! Running on a VPS is generally safer and more isolated. Here's why:
โ VPS Benefits
| Aspect | Your Mac | VPS |
| -------------------- | -------------------- | ------------------------- |
| **Sandboxing** | Limited (host OS) | Full container isolation |
| **Uptime** | Sleeps/disconnects | 24/7 always-on |
| **Network exposure** | Your home IP | VPS IP (firewall control) |
| **Destructive commands** | Access to _your_ files | Access to container only |
| **Persistence** | Laptop off = bot off | Runs forever |
โ ๏ธ What "sandboxed" actually means
โข The Gateway runs in Docker (or as a systemd service)
โข If something goes wrong, you just destroy/recreate the container
โข Your personal files (~/Documents, etc.) are never touched
โข The bot operates in its own /home/node/.clawdbot/ and ~/clawd/ directories
๐ Security best practices
- Bind to loopback or internal โ Don't expose the Gateway port publicly
- Use SSH tunnel โ Access from your laptop/mobile via encrypted tunnel
- Firewall โ Only allow SSH (22) from your IPs
- Tokens โ Keep gateway tokens private
The Hetzner guide I linked earlier walks through exactly this setup with Docker isolation. It's the recommended approach for anyone who wants a "set it and forget it" bot that won't accidentally touch their personal machine. ๐ฆ
@primal path This version of Antigravity is no longer supported. Please update to receive the latest features!