Skip to main content
The Mobilerun Assistant is a hosted virtual assistant you chat with in the dashboard at cloud.mobilerun.ai. You tell it what you want done, and it works on a real cloud phone on your behalf, then reports back with the result. Think of it as an operator for your Mobilerun account. It can set up and manage devices, run apps, handle accounts and logins, scrape data, and build recurring automations, all from a chat window. You don’t write scripts or call an API. You describe a goal, and it figures out the steps.

What it can do

Devices

Provision a Cloud Phone or Pay as you go device, or point you to connecting your own.

Apps and accounts

Install apps, log in, and manage credentials on a device.

Scraping and results

Collect data from an app or page and hand it back as a file or a table.

Workflows

Turn a task into a recurring or triggered automation.

Notifications

Tell you by webhook when it finishes, fails, or needs input.

Files

Produce downloads, screenshots, and other artifacts from a run.

Integrations

Read Gmail, Calendar, Drive, GitHub, Slack, and Teams, and post to Slack, Teams, or OneDrive.

Recordings

Record the phone screen while it works and play it back in the chat.
It also answers questions about Mobilerun itself: plans and credits, what a job might cost, and where to start if you want to build with the SDK or API instead. For developer questions it points you to the right docs page and example rather than teaching code in the chat.

What it is not

The assistant is a chat interface, not the raw automation layer underneath it. It is not the task agent that developers call directly to drive a device step by step. For that, see Agent configuration. It is also not a developer SDK. If you want to build your own integration that talks to the assistant over an API, or teach another AI agent to hold this conversation for you, see Mobilerun Assistant · chat and the MCP Server page.

How a conversation works

1

You ask

Describe what you want in plain language. No commands, no tool names.
2

It plans

The assistant figures out which device, app, or account the task needs.
3

It may ask back

If something is ambiguous or sensitive, it pauses and asks you a question or asks for approval before continuing.
4

It works on a phone

It runs the task on a real cloud phone, taking as many steps as the goal needs.
5

It presents results

It leads with the outcome: what succeeded, what failed, and any file or link you need.
The assistant never completes a purchase for you. When money is involved, it shows you a card in the dashboard and you click it. See Limits and costs.

Where to go next

Getting started

Your first conversation, first device, and first result.

Devices

Cloud phones, pay as you go, apps, accounts, proxies, numbers, and mailboxes.

Results

How scraped data, diffs, and files are collected and presented.

Workflows

Recurring and triggered automation built entirely in chat.

Notifications

Get notified by webhook when a run finishes, fails, or needs you.

Integrations

Connected services: what the assistant can read and where it can write.

Tasks and recordings

Where device work shows up, and how to record the screen.

Human in the loop

How questions and approvals work, and how to walk away and come back.

Memory and skills

What the assistant remembers and how to teach it a new app.

Limits and costs

How credits work and what stops a run from getting out of hand.