OpenClaw · Android Control

The Mobilerun Android-control skill teaches an AI agent to drive a real Android phone: take screenshots, tap and swipe, type, manage apps, and run autonomous tasks — all without any manual API wiring. OpenClaw is the agent CLI that loads it, so you can tell the agent things like “open Instagram and like the latest post” or “go to Amazon and add the cheapest USB-C cable to my cart,” and it executes those tasks on your device.

What the skill includes

File	Purpose
`SKILL.md`	Entry point — authentication flow, device setup, quick-reference table, common patterns
`api.md`	Platform API — device provisioning, AI agent tasks, webhooks, app library
`phone-api.md`	Phone control API — screenshot, UI state, tap, swipe, type, app management
`setup.md`	Authentication and device connectivity guide
`subscription.md`	Plans, pricing, credits, and device types

What it enables

Once installed and given an API key, the agent gains two ways to control a device:

Direct phone control

Step-by-step device interaction: screenshot, tap, swipe, type, press keys, open apps. Best for quick, precise actions.

Autonomous agent tasks

Submit a natural-language goal ("Book a table for 2 at 7pm") and the Mobilerun AI agent executes it on the device end-to-end. Requires credits.

Prerequisites

OpenClaw CLI installed
A Mobilerun account at cloud.mobilerun.ai
An Android device connected via the Mobilerun Portal app, or a cloud-hosted device (Cloud Phone or Physical Phone)

Step 1 — Install the plugin

openclaw plugins install @mobilerun/openclaw-mobilerun

This downloads the Mobilerun skill from the npm registry and registers it with your local OpenClaw installation. Verify it installed correctly:

openclaw plugins list

You should see @mobilerun/openclaw-mobilerun in the output.

Not using OpenClaw? Download the pre-packaged skill and load it into any compatible runtime:

mobilerun.skill

Download the latest release from GitHub

Step 2 — Get your API key

Go to cloud.mobilerun.ai/api-keys (sign in with Google, GitHub, or Discord if prompted)
Click New key, give it a name, and copy the key — it starts with dr_sk_ and is shown only once

Step 3 — Configure the API key

You have two options. Choose whichever fits your workflow:

Option A — Environment variable (quickest)

export MOBILERUN_API_KEY=dr_sk_your_key_here

Add this to your shell profile (~/.zshrc, ~/.bashrc, etc.) to make it permanent.

Option B — OpenClaw config file

OpenClaw stores skill configuration in ~/.openclaw/openclaw.json. Add your key under skills.entries.mobilerun.apiKey:

{
  "skills": {
    "entries": {
      "mobilerun": {
        "apiKey": "dr_sk_your_key_here"
      }
    }
  }
}

If the file already exists, merge this key in — do not replace the entire file.

The config file method is preferred when you use multiple skills with different credentials, since each skill’s key is namespaced separately.

Step 4 — Connect a device

If you don’t have a device connected yet, install the Mobilerun Portal app on your Android phone:

On your Android phone, open Chrome and go to droidrun.ai/portal
Download and install the APK (tap “Install anyway” if Android warns about unknown sources — this is expected)
Open the Portal app and tap Enable Now to grant the Accessibility permission
Long-press “Connect to Mobilerun” to open the API key dialog
Paste your dr_sk_... key and tap Connect

Once connected, the device appears as ready in the Mobilerun dashboard and the agent can use it immediately.

Cloud-hosted devices (Cloud Phones and Physical Phones) are also available if you don’t want to connect a personal device.

Step 5 — Start the agent with the Terminal User Interface (TUI)

openclaw tui

OpenClaw loads the Mobilerun skill and the agent is ready. Try a prompt:

Open the Settings app and tell me the Android version on my phone.

The agent will:

Confirm the API key and find your connected device
Take a screenshot of the current screen
Navigate to Settings and read the relevant UI elements
Report the Android version back to you

How the agent uses the skill

The agent follows a structured initialization flow on every session:

Checks for an API key — looks in MOBILERUN_API_KEY env var or the OpenClaw config file. If missing, it asks the user once.
Verifies the key and discovers devices — calls GET /devices. A 200 response with a ready device means the agent proceeds immediately.
Guides setup only when needed — if no device is found, the agent walks the user through installing the Mobilerun Portal app and connecting.
Executes the request — once a ready device is confirmed, the agent completes the user’s task without additional prompts.

Configuration reference

Method	Location	Key path
Environment variable	Shell environment	`MOBILERUN_API_KEY`
Config file	`~/.openclaw/openclaw.json`	`skills.entries.mobilerun.apiKey`

The skill checks MOBILERUN_API_KEY first. If that is not set, it falls back to the config file. If neither is present, the agent will ask you for the key during the session and offer to save it.

Available LLM models for agent tasks

When submitting autonomous tasks, you can specify which model drives the agent. The Agent page holds the canonical catalog of llmModel values. To see the live list your account can use, call GET /v1/models, or use client.models.list() in the SDK.

Troubleshooting

Agent says the API key is invalid

Keys always start with dr_sk_. If yours looks different, copy it again from cloud.mobilerun.ai/api-keys. Keys can be revoked — create a new one if needed.

No device found

The agent will tell you the device status. If no device appears:

Make sure the Mobilerun Portal app is open on your phone
Check that the Accessibility permission is still enabled (some phones disable it after reboot)
Confirm the phone has a stable internet connection

Device shows as disconnected

The Portal app lost its connection. Open the app on your phone — it usually reconnects automatically. If not, tap Connect again.

Task fails with a billing error

Autonomous agent tasks (POST /tasks) require credits. Check your credit balance at cloud.mobilerun.ai/billing.

Next steps

Agent Skills overview

Learn what Mobilerun skills are and how the agent uses them.

Mobilerun Assistant

Talk to the virtual assistant over chat, with human-in-the-loop cards.

API Keys

Manage your Mobilerun API keys.

Mobilerun Portal

Set up your personal Android device.

Introduction

Concepts

Guides

Dashboard

Agent Skills

Integrations

OpenClaw · Android Control

What the skill includes

What it enables

Direct phone control

Autonomous agent tasks

Prerequisites

Step 1 — Install the plugin

mobilerun.skill

Step 2 — Get your API key

Step 3 — Configure the API key

Option A — Environment variable (quickest)

Option B — OpenClaw config file

Step 4 — Connect a device

Step 5 — Start the agent with the Terminal User Interface (TUI)

How the agent uses the skill

Configuration reference

Available LLM models for agent tasks

Troubleshooting

Next steps

Agent Skills overview

Mobilerun Assistant

API Keys

Mobilerun Portal

​What the skill includes

​What it enables

Direct phone control

Autonomous agent tasks

​Prerequisites

​Step 1 — Install the plugin

mobilerun.skill

​Step 2 — Get your API key

​Step 3 — Configure the API key

​Option A — Environment variable (quickest)

​Option B — OpenClaw config file

​Step 4 — Connect a device

​Step 5 — Start the agent with the Terminal User Interface (TUI)

​How the agent uses the skill

​Configuration reference

​Available LLM models for agent tasks

​Troubleshooting

​Next steps

Agent Skills overview

Mobilerun Assistant

API Keys

Mobilerun Portal

What the skill includes

What it enables

Prerequisites

Step 1 — Install the plugin

Step 2 — Get your API key

Step 3 — Configure the API key

Option A — Environment variable (quickest)

Option B — OpenClaw config file

Step 4 — Connect a device

Step 5 — Start the agent with the Terminal User Interface (TUI)

How the agent uses the skill

Configuration reference

Available LLM models for agent tasks

Troubleshooting

Next steps