What makes Mobilerun notable?

2K downloads. Trust evidence available

How should Mobilerun be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Mobilerun

Load this skill whenever the user wants to control, automate, or interact with a phone or mobile device. This includes: tapping, swiping, typing, taking scre...

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

2.0k

Updated

Oct 9, 2026

Version

2.1.0

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 2K downloads reported by the source. Last updated 10/9/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 9, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 9, 2026
Adoption signal: 2K downloadsadoption · observed Oct 9, 2026
Latest release: 2.1.0release · observed Apr 7, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s173z7qbbaxsxy40z5fhdspgn5840sgr:mobilerun

Install using `clawhub skill install s173z7qbbaxsxy40z5fhdspgn5840sgr:mobilerun` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/johnmalek312/mobilerun before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-johnmalek312-mobilerun/snapshot"

Documentation

CLAWHUB

147,678 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: mobilerun
description: >
  Load this skill whenever the user wants to control, automate, or interact with a phone
  or mobile device. This includes: tapping, swiping, typing, taking screenshots, reading
  the screen, managing apps, running AI agent tasks on a phone, or any form of phone/mobile
  automation. Also load when the user mentions Mobilerun, Droidrun, or phone control.
  Currently supports Android devices, with iOS support coming soon.
  Requires a Mobilerun API key (prefixed dr_sk_) and a connected device.
tags: [android, mobile, automation, phone-control, testing, social-media, scraping, app-testing]
metadata: { "openclaw": { "emoji": "📱", "primaryEnv": "MOBILERUN_API_KEY", "requires": { "env": ["MOBILERUN_API_KEY"], "bins": ["curl", "jq"] } } }
---

# Mobilerun

The hosted mobile cloud platform. Grant AI native control of Android devices to tap, swipe, type, navigate apps, fill out forms, extract data, automate workflows, and run QA. Connect your own phone, spin up on-demand virtual devices, or use always-on emulated and physical devices in the cloud. iOS support coming soon.

Base URL: `https://api.mobilerun.ai/v1`
Auth: `Authorization: Bearer <MOBILERUN_API_KEY>`

**Important:** The base domain (`https://api.mobilerun.ai/`) returns 404. You must always include `/v1` in the path. All API calls should be made via `curl`. Example:

```bash
curl -s https://api.mobilerun.ai/v1/devices \
  -H "Authorization: Bearer $MOBILERUN_API_KEY"
```

## Quick Start

The API key (`MOBILERUN_API_KEY`) is already available -- OpenClaw handles credential setup before this skill loads. Do NOT ask the user for an API key. Just use it.

1. **Check for a ready device:**
   ```bash
   curl -s https://api.mobilerun.ai/v1/devices \
     -H "Authorization: Bearer $MOBILERUN_API_KEY"
   ```
   - `state: "ready"` = **good to go, skip to the user's request**
   - No devices or `state: "disconnected"` = see step 2
   - `401` = invalid,expired, or revoked key  -- ask user to check https://cloud.mobilerun.ai/api-keys

2. **No ready device?** Tell the user and suggest a fix:
   - No devices at all = guide them to set up Portal APK (see [references/setup-and-billing.md](./references/setup-and-billing.md))
   - `disconnected` = ask user to reopen Portal app and tap Connect

3. **Take a screenshot to confirm** (optional, only if first action fails):
   ```bash
   curl -s https://api.mobilerun.ai/v1/devices/{deviceId}/screenshot \
     -H "Authorization: Bearer $MOBILERUN_API_KEY" -o screenshot.png
   ```
   If this returns a PNG image, the device is working.

Not sure what's possible? See [references/use-cases.md](./references/use-cases.md) for examples.

**Key principle:** If a device is ready, go straight to executing the user's request. Don't walk them through setup they've already completed.

**Be smart about context gathering:** Before taking actions or asking the user questions, use available tools to understand the situation. List packages to find the r

_meta.json

{
  "ownerId": "kn740pdc7mh9s1d3x1pkgc6h2h81cpyt",
  "slug": "mobilerun",
  "version": "2.1.0",
  "publishedAt": 1775558897125
}

references/changelog.md

# Changelog

All notable changes to the Mobilerun skill are documented here. Format follows [Keep a Changelog](https://keepachangelog.com/).

## [Unreleased]

### Added
- Troubleshooting guide with 10 common issues (references/troubleshooting.md)
- Searchable tags in SKILL.md frontmatter for ClawHub discovery
- Unicode/multi-language support documented for POST /keyboard
- Use case examples for non-developers (references/use-cases.md)
- Social proof: GitHub stars, TECNO EllaClaw OEM adoption, arXiv citation
- Active development links (PyPI, ClawHub listing)
- Resources section with community and documentation links
- Changelog

### Changed
- Restructured into references/ folder (setup-and-billing, troubleshooting, security, use-cases) for on-demand context loading
- Renamed "Before You Start" to "Quick Start"
- Rewrote intro paragraph with cloud device types (on-demand virtual, emulated, physical)

## [1.0.1] - 2026-02-10

### Changed
- Restructured as OpenClaw plugin monorepo
- Converted plugin to flat skill format

## [1.0.0] - 2026-02-08

### Added
- Initial release
- Device management API (list, provision, terminate cloud devices)
- Screen observation (screenshot, UI accessibility tree)
- Phone control (tap, swipe, type, press key, open/close apps)
- Tasks API for AI agent automation
- reference.md with auth setup, Portal APK guide, plans & billing, webhooks
- OpenClaw plugin metadata and CI packaging workflow

references/security.md

# Security & Privacy

This document describes how the Mobilerun skill handles sensitive data, credentials, and device permissions.

## Data Handling

- **Screenshots and UI tree data** may contain personal information visible on the user's screen (messages, emails, photos, etc.). This data is fetched on-demand for the current task and is not stored, cached, or transmitted beyond the API response.
- All API calls go to `https://api.mobilerun.ai/v1` over HTTPS.
- The skill does not collect analytics, telemetry, or usage data.

## Credentials

- The `MOBILERUN_API_KEY` (prefixed `dr_sk_`) is provided by the host platform (OpenClaw) and used solely for authenticating API requests.
- The key is never displayed, logged, or included in user-facing output.
- Keys can be created, rotated, or revoked at any time from https://cloud.mobilerun.ai/api-keys.

## Device Permissions

The Droidrun Portal app on the user's Android device requires the **Accessibility Service** permission. This is the same system API used by screen readers and assistive technology. It allows the skill to:

- Read the UI element tree (text, buttons, layout)
- Simulate taps, swipes, and text input
- Identify the foreground app

The user grants this permission explicitly during setup and can revoke it at any time in Android Settings.

## APK Installation

The Portal app is distributed as an APK from GitHub Releases (open source: https://github.com/droidrun/droidrun-portal). Because it is installed outside the Play Store, Android shows a standard sideloading warning. This is expected behavior for any app not distributed through the Play Store.

## Input Handling

API endpoint paths in the documentation use placeholders like `{deviceId}`, `{packageName}`, and `{task_id}`. These are UUIDs or Android package name strings returned by the API itself (e.g. from `GET /devices`). They are not user-supplied free text. When constructing curl commands, always use values obtained directly from prior API responses — never interpolate raw user input into URLs or shell commands.

## Scope of Control

The skill can only interact with devices that the user has explicitly connected to their Mobilerun account. It cannot access devices belonging to other users, and all actions require a valid authenticated API key.

references/setup-and-billing.md

# Setup & Billing

## Authentication

### How It Works

Mobilerun uses API keys for programmatic access. All API calls go to `https://api.mobilerun.ai/v1`
with the key in the Authorization header:

```
Authorization: Bearer dr_sk_...
```

- Keys are always prefixed with `dr_sk_` -- if a user provides something without this prefix, it's not a valid Mobilerun key
- Keys are created from the Mobilerun dashboard and can be revoked or expired
- Each key is tied to a single user account

### Getting an API Key

The user needs to:

1. Go to **https://cloud.mobilerun.ai/api-keys**
- If not logged in, the page redirects to login first (Google, GitHub, or Discord -- no email/password option)
- After login it redirects back to the API keys page
2. Click the **"New Key"** button
3. Give the key a name (anything descriptive is fine)
4. Copy the full key -- it's only shown once at creation time

The key will look like: `dr_sk_a1b2c3d4e5f6...`

### Troubleshooting Auth Issues

**User provides a key that doesn't start with `dr_sk_`:**
- It's not a Mobilerun API key. Ask them to copy it again from https://cloud.mobilerun.ai/api-keys

**401 on a key that previously worked:**
- The key may have been revoked or expired. Ask the user to check the API keys page and create a new one if needed

**User says they can't find the API keys page:**
- Direct them to https://cloud.mobilerun.ai/api-keys -- they need to be logged in first

**User doesn't have an account:**
- They can create one by going to https://cloud.mobilerun.ai/sign-in and signing in with Google, GitHub, or Discord. First login automatically creates an account.

---

## Device Setup (Portal APK)

A personal device is the user's own Android phone connected to Mobilerun via the Droidrun Portal app.

Guide the user step by step through the setup process.

### Step 1: Download the Portal APK

1. On the Android device, open Chrome and go to **https://droidrun.ai/portal**
2. This redirects to the GitHub releases page for the Portal app
3. Scroll down to the **"Assets"** section at the bottom of the latest release
4. Tap the file named **`droidrun-portal-vx.x.x.apk`** (the version number varies) -- this is the APK file to download
- Do NOT tap "Source code (zip)" or "Source code (tar.gz)" -- those are the source code, not the app

### Step 2: Install the APK

1. Once downloaded, tap the APK file to install it (or find it in Downloads)
2. **Android may show a sideloading prompt** -- this is standard for apps distributed outside the Play Store (like beta apps or open-source projects):
- Droidrun Portal is open source: https://github.com/droidrun/droidrun-portal
- Follow the on-screen prompts to complete installation

### Step 3: Enable Accessibility

1. Open the Droidrun Portal app
2. A red banner at the top says **"Accessibility Service Not Enabled"** -- tap **"Enable Now"**
3. This opens Android Settings. Find **"Droidrun Portal"** in the list of accessibility services
4. Tap on it and **toggle it on

Github ReposUpdated 2h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.