Skip to main content
The Mobilerun agent is an AI-powered automation system that executes tasks on Android devices. Configure the agent with a prompt and settings, then run it on any connected device.

Overview

The agent:
  • Interprets natural language instructions
  • Interacts with device UI elements
  • Executes multi-step workflows autonomously
  • Returns results and structured output

Configuration

Task Prompt

The prompt describes what the agent should do. Write clear, specific instructions for best results.

Model Selection

Choose the LLM model that powers the agent. Different models offer different tradeoffs: Pass one of the following identifiers as the llmModel parameter in the REST API or the SDK, or select it in the Playground. This table is the canonical catalog of models available for cloud agent tasks.
The model lineup changes over time. To see the live list your account can use, call GET /v1/models, or use client.models.list() in the SDK. That endpoint is the source of truth whenever an identifier here returns a “model unavailable” error.
This model list applies to Mobilerun Cloud. For the open source Framework, choose a provider and model in the Framework configuration.

Execution Limits

Features

Reasoning Mode

Enables logical thinking and step-by-step analysis. The agent will reason through complex tasks before acting.

Vision

Allows the agent to process and understand visual content on screen. Required for most UI automation tasks.

Natural input

Paces taps, swipes, and typing naturally instead of sending instant input. Set with the stealth parameter.

Platform Settings

Structured Output

Define a JSON schema to receive structured responses from the agent. This is useful for:
  • Data extraction tasks
  • Validation workflows
  • Integration with downstream systems
When a schema is defined, the agent formats its output to match the specified structure.

Task Recording

Set recordingEnabled: true when you create a task to capture a video of the device screen for the whole run. Recording starts when the task enters the running state and stops when the task completes, fails, or is cancelled. Once the recording has started, the task’s status, list, and detail responses include two extra fields: Both fields are null while the task is still queued, when recording is disabled, or if the recording could not be started. Recording is best-effort. A recording failure never changes the task outcome. Recording requires a device that supports video capture. If you create a task with recordingEnabled: true on a device that does not support recording, the API rejects it with a 400 response and a DEVICE_RECORDING_UNSUPPORTED error. Set recordingEnabled to false or choose a device that supports recording. If the device reports the unsupported capability only after the task has started, the task fails instead of silently running without a recording.

Running the Agent

Via Playground

Use the Playground for interactive testing:
  1. Configure your task and settings
  2. Select a device
  3. Click Run
  4. Monitor execution in the task stream

Via API

Run tasks programmatically using the API:

Via MCP

Use the MCP integration to run tasks from AI assistants and IDEs.

Execution Flow

  1. Initialization - Agent connects to the selected device
  2. Observation - Agent captures the current screen state
  3. Planning - Agent determines the next action based on the prompt
  4. Action - Agent executes the action (tap, type, scroll, etc.)
  5. Repeat - Steps 2-4 repeat until the task is complete or limits are reached
  6. Output - Agent returns results and any structured output

Best Practices