Talk to one agent. Let your phone act, learn, and connect.
Website · Paper · Android App · Install · FAQ · Security · Contributing · LinkedIn · YouTube · Bilibili
ClawMobile is an agent-first phone runtime for Android. It explores what phones could become when the primary interface is an agent instead of manual app switching: the agent can use local tools and files, observe Android state, control apps with permission, learn reusable mobile skills, and communicate with trusted agents.
Instead of treating the phone as a remote screen, ClawMobile makes it the runtime. The phone hosts the gateway, the mobile tools, the recorded evidence, and the learned workflows, so personal app tasks can become repeatable skills instead of one-off screenshot reasoning sessions.
The Android companion app is the recommended way to try ClawMobile. It sets up the Termux runtime over SSH, starts the local service, and gives you a phone-native UI for tasks, skills, runtime status, logs, and trusted-agent messaging.
Download the latest ClawMobile Companion APK, or read the Android app guide.
|
|
|
| Monitor the runtime | Start tasks | Connect with trusted contacts |
- Download the latest APK from the ClawMobile release page.
- Open the ClawMobile app and follow the guided setup.
- Start ClawMobile from the app, then use Tasks, Skills, Social, and Settings.
The app guides the Termux runtime setup internally, then provides a status dashboard, task chat, skills library, logs, and trusted-agent messaging on top of that local service.
Install Termux from F-Droid first. If F-Droid is unavailable, use the official Termux GitHub releases. The Google Play Termux build is not the supported ClawMobile install path.
Then run in Termux:
# Install ClawMobile with the guided quick setup and start the gateway
curl -fsSL https://raw.githubusercontent.com/ClawMobile/ClawMobile/main/installer/termux-lite/bootstrap.sh | bash -s -- --quick --startFrom an existing repository checkout:
./installer/termux-lite/clawmobile setup --quick --startOmit --start if you want setup to finish before launching the long-running
OpenClaw gateway.
Quick setup will ask for a model provider/API key and, optionally, Telegram bot details so you can message the phone from another device. If those terms are unfamiliar, see the FAQ before starting.
More setup paths:
After the gateway starts, try:
What can you do on this phone?
What phone capabilities are available right now?
More demos, including skill learning and Android task examples, are in the demo gallery. Runtime capability details are in the runtime reference.
Mobile agents should not just watch a phone screen from the outside. ClawMobile puts the runtime on the Android device, where the apps, files, notifications, and user-approved control channels already live.
| Capability | Why it matters |
|---|---|
| One agent-facing phone surface | The agent can use local files, shell tools, Android state, screenshots, and app control from the same runtime. |
| Progressive user control | Start with Termux tools, then add Termux:API, ADB, app control, and trusted-agent messaging only when the user enables them. |
| From repeated UI work to reusable skills | Demonstrations and successful runs can become durable app knowledge instead of one-off screen reasoning. |
This makes ClawMobile useful today as a phone-side OpenClaw gateway, a personal mobile assistant, a generated-skill testbed, and a practical bridge between language-agent reasoning and deterministic Android actions.
| Layer | Role |
|---|---|
| User channel | Android app, Telegram, or another OpenClaw-supported interface. |
| OpenClaw gateway on Android | The local agent runtime running on the phone. |
| ClawMobile workspace | Policies, reusable skills, and generated-skill artifacts. |
mobile-ui plugin |
Tool bridge between OpenClaw and mobile backends. |
| Mobile backends | Termux tools, Termux:API, ADB/Android shell, optional OCR, and generated skill storage. |
| Android apps and device state | The real mobile environment the agent observes and acts on. |
The important design choice is progressive capability. The same agent can run with only Termux permissions, then use richer phone-control tools when the user authorizes them.
ClawMobile is a public preview for real Android devices. It runs locally in Termux, can use strong phone-control capabilities when authorized, and may store sensitive runtime artifacts such as API keys, screenshots, traces, logs, and generated-skill evidence.
Read the status and limitations and security policy before sharing traces, logs, or generated skills.
-
openclaw-plugin-mobile-ui/Mobile runtime plugin, Android/Termux/ADB/OCR tools, recorder, trace parser, generated-skill pipeline, and Termux runtime batch fast path. -
installer/termux-lite/Current Termux runtime scripts. The directory name is historical; this is the maintained default runtime onmain. -
installer/workspace-seed-lite/Default OpenClaw workspace seed, policies, and trace-induction skills.
- Use the Android app: docs/android-companion-app.md
- Install ClawMobile: installer/INSTALL.md
- Runtime reference: installer/termux-lite/README.md
- Status and limitations: docs/status-and-limitations.md
- Troubleshoot setup: installer/FAQ.md
- Report issues safely: SECURITY.md
- Contribute fixes or skills: CONTRIBUTING.md
- Follow public changes: CHANGELOG.md
- Read the paper: https://arxiv.org/abs/2602.22942
@misc{du2026clawmobile,
title = {ClawMobile: Rethinking Smartphone-Native Agentic Systems},
author = {Du, Hongchao and Wu, Shangyu and Li, Qiao and Pan, Riwei and Li, Jinheng and Sun, Youcheng and Xue, Chun Jason},
year = {2026},
eprint = {2602.22942},
archivePrefix= {arXiv},
primaryClass = {cs.MA},
doi = {10.48550/arXiv.2602.22942}
}


