Skip to main content
OpenClaw is an agent CLI that loads skills — structured knowledge packs — to give AI agents access to external APIs and services. Installing the Mobilerun skill in OpenClaw lets you 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 a real Android phone.

​
Prerequisites

​
Step 1 — Install the Plugin

This downloads the Mobilerun skill from the npm registry and registers it with your local OpenClaw installation. Verify it installed correctly:
You should see @mobilerun/openclaw-mobilerun in the output.

​
Step 2 — Get Your API Key

  1. Go to cloud.mobilerun.ai/api-keys (sign in with Google, GitHub, or Discord if prompted)
  2. 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)

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:
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:
  1. On your Android phone, open Chrome and go to droidrun.ai/portal
  2. Download and install the APK (tap “Install anyway” if Android warns about unknown sources — this is expected)
  3. Open the Portal app and tap Enable Now to grant the Accessibility permission
  4. Long-press “Connect to Mobilerun” to open the API key dialog
  5. 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 loads the Mobilerun skill and the agent is ready. Try a prompt:
The agent will:
  1. Confirm the API key and find your connected device
  2. Take a screenshot of the current screen
  3. Navigate to Settings and read the relevant UI elements
  4. Report the Android version back to you

​
Configuration Reference

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.

​
Troubleshooting

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.
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
The Portal app lost its connection. Open the app on your phone — it usually reconnects automatically. If not, tap Connect again.
Autonomous agent tasks (POST /tasks) require credits. Check your credit balance at cloud.mobilerun.ai/billing.

​
Next Steps

Agent Skills overview

Learn what the Mobilerun skill includes and how the agent uses it.

API Keys

Manage your Mobilerun API keys.

Mobilerun Portal

Set up your personal Android device.

Credits & Plans

Understand plans, credits, and device types.