Public preview for real Android devices

Run a phone-native AI agent from Android.

ClawMobile pairs a native Android companion app with a Termux-hosted OpenClaw runtime, so tasks, generated skills, trusted-agent messaging, logs, and setup controls stay close to the device they operate.

Download Android APK Watch demos View source

Available now on the App Store Google Play coming soon

Android companion Recommended first control surface for setup, tasks, skills, logs, and social contacts.

Termux runtime OpenClaw, the local companion server, skills, artifacts, and logs still run inside Termux.

Generated skills Teach by demonstration, promote the trace, then reuse the workflow from natural language.

Runtime protocol v1 Draft HTTP JSON contract for Android now and future iOS, desktop, cloud, or LAN runtimes.

Current package

One companion app. One local runtime. One OpenClaw workspace.

The public-preview runtime includes the installer, OpenClaw mobile plugin, optional OCR support, ADB-backed UI tools, and the trace-to-skill workflow. The Android app is the daily control shell; Termux remains the source of truth.

Control

Tasks from a native UI

Send requests, follow long-running work, receive task completion notifications, and inspect runtime status without living in a terminal.

Runtime

OpenClaw in Termux

ClawMobile installs and maintains OpenClaw, the companion server, package dependencies, generated skills, logs, and runtime state locally.

Device control

ADB-backed UI tools

ADB enables richer phone-control capabilities through authorized Android developer options, USB, or wireless connections.

Sharing

Trusted contacts

Create an Agent ID, exchange messages with trusted ClawMobile devices, and share generated skills for review and import.

Android companion app

Install the APK, then let the app guide Termux setup.

The companion app does not replace Termux. It uses SSH for setup and maintenance, then talks to the local companion server for tasks, skills, status, logs, and trusted-agent messaging.

Latest documented release

ClawMobile-v0.2.3.apk

Download the release-signed APK from the public ClawMobile release page. If you installed an earlier debug-signed test APK, uninstall it before installing this release.

Download APK Release page

Inside Termux

What still runs locally

OpenClaw gateway and ClawMobile runtime
Local companion HTTP server
Package installs and setup scripts
Workspace skills, artifacts, logs, and runtime state

Mobile stores

Available now on the App Store. Google Play is coming soon.

Download the iOS app from the App Store. For Android, the GitHub release APK remains the current public-preview install path while the Google Play listing is prepared.

Google Play the App Store

App surfaces

What the companion adds

Guided Termux setup from a native Android screen
Status checks for SSH, companion server, OpenClaw, ADB, model key, and workspace skills
Task chat, skills browser, task notifications, social contacts, and debug logs

Local channels

How it connects

SSH to Termux for setup, maintenance, and runtime start commands
Local HTTP to the companion server for daily app interactions
The Android app controls and observes the local runtime; it is not the runtime itself

Recommended setup flow

Start with Termux, then operate from the app.

ADB is optional, but it unlocks richer phone-control capabilities. Follow the current ADB authorization flow in the main setup guide when you need UI automation.

Install Termux

Use F-Droid or the official Termux GitHub releases for the Android runtime environment.

Run SSH setup

Use the commands shown in the companion app to prepare local SSH access into Termux.

Pair the app

Connect using the local SSH host, port, and username so the app can manage setup.

Run setup

Let the app install and maintain the ClawMobile runtime inside Termux.

Start ClawMobile

Use Tasks, Skills, Social, status, and logs from the Android companion app.

Generated skills preview

Teach the phone by doing the task once.

ClawMobile records a demonstration, turns the trace into a reusable OpenClaw skill, and can run that skill later from a natural-language request. The goal is durable local evidence, not hard-coded app scripts.

Record

Perform the task once on the phone from the target app and starting state.

Capture

Collect touch events, screenshots, app state, UI evidence, and values that should become parameters.

Generate

Create a parameterized skill candidate with recovery hints and reusable action structure.

Promote

Move the candidate into the OpenClaw workspace once it is ready to reuse.

Improve

Attach execution feedback or additional demos when layouts, devices, or list states vary.

Preview reliability

Generated skills are useful today, but they are still preview software.

They work best on the same device, app version, and starting state used for the demonstration. Fast paths and batch execution are experimental accelerators for stable steps, not a replacement for normal UI recovery.

Runtime protocol v1

A draft shared contract for multiple runtimes.

The v1 protocol gives clients a stable HTTP JSON task API and capability description. Backends can differ by platform while clients rely on the same core health, capability, run creation, run list, and run status surface.

Required endpoints

Small common task API

GET/v1/health

GET/v1/capabilities

POST/v1/runs

GET/v1/runs?limit=100

GET/v1/runs/{runId}

Compatibility model

Capabilities decide what clients show

HTTP JSON is the baseline transport; WebSocket events are optional.
Clients can poll run status when streaming is unavailable.
Capability discovery advertises available tools, feature states, extensions, risk, and approvals.
Remote LAN, Tailscale, desktop, and cloud runtimes should require explicit pairing tokens.

Demo gallery

One request in. The phone moves.

The gallery includes command-channel demos, generated-skill reuse, hardware and system checks, browser search, maps routing, shopping comparison, and script execution.

Open demo docs

Generated Google Keep skill

Record a phone workflow once, promote it as a generated OpenClaw skill, then reuse it from a request.

Hardware demo

Inspect device information and runtime health from the phone-control surface.

System demo

Exercise Android system-level controls through the local runtime.

Script demo

Execute repeatable local actions and inspect the result from the device workflow.

Chrome demo

Open a browser flow, search, and recover through real mobile UI state.

Maps demo

Use app automation for navigation-oriented tasks from a simple instruction.

Shopping comparison

Compare mobile app results across stores and act on the best candidate.

Status and limitations

Public preview means real devices, real setup, and clear boundaries.

ClawMobile is available for real Android devices, but generated skills, ADB-backed control, and screenshot-heavy verification still have practical constraints during preview.

Known limits

ADB, device state, and network conditions matter.

ADB-backed UI control requires Android developer options, USB or wireless ADB, and an authorized device connection. Termux mirrors can be stale or unreachable, and screenshot-heavy verification may be slower on phone hardware than desktop.

Release hygiene

The active path is Android companion plus Termux runtime.

Generated skills should first be tested on the same device, app version, and starting app state used for the demo.
Cross-device, cross-layout, and dynamic-list workflows may need additional demonstrations.
The older DroidRun/MobileRun backend is archived on the legacy branch and is not the active install path.
Use ClawMobile only on devices you own and in ways that respect app terms and policies.

Waitlist

Join the ClawMobile waitlist.

Leave your email for early access updates, Google Play and App Store launch notifications, and preview invitations.