> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mobilerun.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Devices

> Ask your agent to activate, create, and manage phones, apps, accounts, proxies, numbers, and mailboxes.

Your agent works on the phones already in your account (Cloud Android, Cloud iOS, and Personal Phones, Android and iPhone), or creates a Cloud Android phone when you ask. It can only create Cloud Android phones. It also handles the things a phone needs to be useful: apps, logins, a proxy, and verification codes.

## Cloud Android

Tell your agent what you want to do and it activates a ready phone from your account. If you have several ready phones, it asks which one before touching any of them. Say "switch to my other phone" to change targets mid-conversation.

Ask it to create a phone and it offers two ways to pay for one:

| | Subscription | Pay as you go |
| - | - | - |
| Billing | Counts against a plan slot | Per minute, from your device minutes (plan allowance first, then overage; the Free plan stops when the allowance is used up) |
| When you stop using it | Always on, managed from the dashboard | Stop it to pause billing, or delete it |
| Best for | Logins, apps, anything long-lived | Short tasks, or work you want to pause and pick up later |
| Requires | A plan with a free slot and an active dedicated Mobilerun proxy | A name and a country; it gets a rotating residential IP, billed as residential traffic (GB) |

Your agent confirms before creating either kind. For pay as you go, an explicit request for a pay-as-you-go phone counts as your consent; your agent asks only when your request doesn't clearly accept per-minute billing. If your plan has no free slot or no proxy for a subscription phone, it shows you the purchase card instead of guessing.

### Stop, resume, and delete

A pay-as-you-go phone has three ways to end its work:

* **Stop** pauses the phone. It keeps its apps, logins, files, and identity, and bills no minutes while stopped. Your agent can stop a phone that is ready.
* **Resume** starts a stopped phone again, exactly as you left it. It needs device minutes.
* **Delete** removes the phone and erases everything on it, permanently. Billing stops once the phone is confirmed terminated.

Stop, resume, and delete each show an approval card first. Subscription and Personal Phones have no stop or resume; they stay on, and subscription phones are released from the dashboard, not through chat.

When a pay-as-you-go phone runs out of device minutes, it is stopped and keeps its data. Add minutes, then ask your agent to resume it.

> [!WARNING]
>
> Deleting a pay-as-you-go phone erases everything on it, permanently. If you only want to pause it, stop it instead. For accounts you want to stay signed in for the long term, ask for a Cloud Android subscription phone.

A reset wipes a phone back to a clean state, apps and accounts included, and takes a few minutes to come back online. It always asks for your approval first, and only runs on a phone that is ready, not one still starting, resetting, or shutting down.

> Give me a Cloud Android phone for the next 20 minutes, I just need to test one signup flow.

> Reset my main phone, it's stuck with a broken app install.

| You can ask | It needs from you | Needs approval |
| - | - | - |
| Activate or switch to a ready phone | Which phone, if more than one is ready | No |
| Create a Cloud Android subscription phone | Confirming the plan slot and proxy | Yes |
| Create a Pay as you go phone | Confirming per-minute billing | Yes, built into the create step |
| Reset a phone | Confirming which phone and that data is lost | Yes |
| Stop or resume a Pay as you go phone | Confirming; resume needs device minutes | Yes |
| Delete a Pay as you go phone | Confirming | Yes |

See [Devices](https://docs.mobilerun.ai/devices.md) for your full device list and live streams, and [Device Types](https://docs.mobilerun.ai/device-types.md) for pricing and specs.

## Installing apps

Your agent tries the Mobilerun App Store first, since it needs no Google account. If an app isn't in the Store, it shows you one card with the options: install from Google Play (needs a Google account signed into the phone), use the website instead, or cancel. There is no Play Store on iOS.

| Source | Needs | Notes |
| - | - | - |
| Mobilerun App Store | Nothing | Curated catalog, the default install path |
| Google Play Store | A Google account signed into the phone | Offered on the card when the app isn't in the Mobilerun Store |
| An app you uploaded | Uploading the file under [Apps](https://docs.mobilerun.ai/apps.md) | Ask your agent to install that app on a phone; it picks it from your Apps library |

> Install TikTok on my Cloud Android phone.

> I uploaded my own build in the Apps tab, put it on my second phone.

If an app needs a Google account and none is set up, your agent asks before starting that setup.

## Accounts and credentials

For any login, signup, or verification, your agent prefers a Cloud Android subscription phone. On a pay-as-you-go phone it warns you first: stopping the phone keeps your logins, but deleting it erases them.

Saved logins live in your credential store, referenced by name only. Your agent never sees, stores, or repeats a password, token, or code back to you in chat. To save a new login, it opens an in-chat card and you type the values there directly, never into the conversation.

Your agent can't attach a credential to a task itself. A saved login is filled in when you attach it in the [Task runner](https://docs.mobilerun.ai/playground.md) credential picker, or when a routine injects it. If neither applies, the app's login screen asks for the password on the phone, and your agent tells you so and waits for you to type it there.

For 2FA, codes from your Mobilerun mailboxes, numbers you rented through your agent, and saved authenticator (TOTP) secrets are filled in automatically. For any other code, you type it on the phone yourself. Your agent never asks you to relay a code in chat.

| You can ask | It needs from you | Needs approval |
| - | - | - |
| Log into an app with a saved credential | The credential attached in the Task runner or a routine | No, beyond the normal login screen |
| Save a new login | Filling in the in-chat credential card | Card is the only path in, no separate approval |
| Handle a 2FA or OTP prompt | Nothing for mailbox, rented number, or saved authenticator codes; otherwise typing the code on the phone | No |

See [Credentials](https://docs.mobilerun.ai/credentials.md) for how the credential store works.

## Proxies

Apps see a Cloud Android phone's network location through its IP address. Many apps restrict or challenge traffic from datacenter IPs, so Mobilerun recommends a proxy for any phone that signs into real accounts.

Ask your agent which proxies you have and it lists them, with which device each one is connected to. Ask it to connect a Mobilerun proxy to a phone and it confirms the change before making it. WireGuard proxies are connected in the dashboard. Cancelling a managed proxy or deleting one you brought yourself needs your approval. Buying a new proxy happens through a purchase card your agent shows you; it never invents a price.

> Set up a dedicated proxy for my Instagram phone.

> Which proxy is my second Cloud Android phone using right now?

See [Proxies](https://docs.mobilerun.ai/proxies.md) for proxy types and setup.

## Phone numbers and SMS verification

Phone numbers are an add-on, not part of your plan. A small per-country amount of capacity may be included. Ask your agent for a number in the country you need, and it reuses an existing number or provisions a new one from included capacity. If none is left, it shows a purchase card instead of creating one for free.

Once a number is assigned, your agent types it into the app, waits for the SMS, and types the code in itself. It stops and reports back if no code arrives within about a minute.

> Verify this signup with a US phone number.

## Mailboxes for email verification

The same pattern applies to email codes and confirmation links. Your agent asks once whether you want a mailbox address it generates automatically or one you name yourself, then creates it from your included capacity. It enters the address, waits for the message, and types the code in itself or continues the confirmation link where it can. If nothing arrives within about a minute, it stops and reports that.

A mailbox only receives mail; it can't send. It is not your personal inbox, so your agent confirms before reusing an existing one for a new signup.

> Create an email inbox for testing this new app.

## Websites and app shortcuts

Apps come first. If there is no app for what you need, or you ask for the web version, your agent opens the site in Chrome on the phone and works there, including logins, search, and pages that load as you scroll. It can switch a site to its desktop layout when the mobile page hides what you need.

For well-known apps such as TikTok, Instagram, X, Reddit, LinkedIn, WhatsApp, Uber, and Gmail, your agent can jump straight to a profile, post, search, or settings screen instead of tapping through menus. That is faster and less likely to break when an app changes its layout. Android only.

> Open the LinkedIn profile for this URL and tell me their current title.

## Connected services

Your agent can also work with services you connect, such as Gmail, Google Calendar and Drive, GitHub, Slack, Microsoft Teams, and OneDrive, and pair that with device work. See [Integrations](https://docs.mobilerun.ai/agents/integrations.md).

## Related

> [card] [Results](https://docs.mobilerun.ai/agents/results.md)
>
> How your agent scrapes lists, diffs runs, and delivers files.

> [card] [Human in the loop](https://docs.mobilerun.ai/agents/human-in-the-loop.md)
>
> How approvals and questions work in chat.

> [card] [Limits and costs](https://docs.mobilerun.ai/agents/limits-and-costs.md)
>
> Credits, step budgets, and what your agent hands off.

> [card] [Credentials](https://docs.mobilerun.ai/credentials.md)
>
> The credential store behind saved logins.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.