> ## 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 the assistant to activate, create, and manage cloud phones, apps, accounts, proxies, numbers, and mailboxes.
The assistant works on cloud phones already in your account, or creates one when you ask. It also handles the things a phone needs to be useful: apps, logins, a proxy, and verification codes.
## Cloud phones
Tell the assistant 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 Cloud Phone | Pay as you go |
| -------------------- | --------------------------------------------- | ------------------------------- |
| Billing | Counts against a plan slot | Per minute, billed from credits |
| State after shutdown | Kept, managed from the dashboard | Erased, the phone is gone |
| Best for | Logins, apps, anything long-lived | A single short task |
| Requires | A plan with a free slot and a dedicated proxy | Nothing extra to set up |
The assistant always confirms before creating either kind. The pay-as-you-go option states the per-minute billing before you confirm it. If your plan has no free slot or no proxy for a subscription phone, it shows you the purchase card instead of guessing.
A pay-as-you-go phone keeps apps, logins, and files only while it stays running. Shutting it down erases everything on it, permanently. For accounts you want to stay signed in, ask for a subscription Cloud Phone instead.
Ending a pay-as-you-go phone needs your approval. The assistant states what you're giving up, then shows an approval card before it shuts the phone down. Billing stops once the phone is confirmed terminated. Subscription phones are released from the dashboard, not through chat.
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 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 subscription Cloud 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 |
| Terminate a Pay as you go phone | Confirming | Yes |
See [Devices](/devices) for your full device list and live streams, and [Device Types](/device-types) for pricing and specs.
## Installing apps
The assistant tries the Mobilerun App Store first, since it needs no Google account. It falls back to the Play Store only when an app isn't in the Store, and only if a Google account is already set up on the phone.
| Source | Needs | Notes |
| ------------------- | -------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| Mobilerun App Store | Nothing | Curated catalog, the default install path |
| Google Play Store | A Google account signed into the phone | Fallback when the app isn't in the Mobilerun Store |
| Your own APK | Uploading the file yourself | The assistant can't push a raw file; upload it under [Apps](/apps), then ask it to install that app on a phone |
> Install TikTok on my cloud 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, the assistant asks before starting that setup.
## Accounts and credentials
For any login, signup, or verification, the assistant prefers a subscription Cloud Phone. On a pay-as-you-go phone it warns you first, because the session disappears at shutdown.
Saved logins live in your credential store, referenced by name only. The assistant 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.
If a 2FA prompt appears, the assistant surfaces it and waits. You read the code from your authenticator and either type it into the phone yourself or tell the assistant to enter it. An SMS code sent to a phone number you rented through the assistant is the one exception it can read on its own.
| You can ask | It needs from you | Needs approval |
| --------------------------------------- | -------------------------------------------------------- | ---------------------------------------------- |
| Log into an app with a saved credential | Which saved login, if you have more than one | 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 | Reading the code to the assistant, or typing it yourself | No |
See [Credentials](/credentials) for how the credential store works.
## Proxies
A Cloud Phone already looks like a real device to the apps it runs. The IP address is the weak point: a raw datacenter IP gets flagged fast, so Mobilerun strongly recommends putting a proxy on any phone doing real account work.
Ask the assistant 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 the assistant shows you; it never invents a price.
> Set up a dedicated proxy for my Instagram phone.
> Which proxy is my second cloud phone using right now?
See [Proxies](/proxies) for proxy types and setup.
## Phone numbers and SMS verification
Your plan includes a number of managed phone numbers you can use to receive SMS verification codes. Ask the assistant for one in the country you need, and it reuses an existing number or provisions a new one from your included capacity. If none is left, it shows a purchase card instead of creating one for free.
Once a number is assigned, the assistant enters it in the app, waits for the SMS, and reads the code back to you or types it in directly. 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. The assistant 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 reads the code back 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 the assistant 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, the assistant 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, the assistant 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
The assistant can also read from services you connect, such as Gmail, Google Calendar and Drive, GitHub, Slack, Microsoft Teams, and OneDrive, and pair that with device work. See [Integrations](/assistant/integrations).
## Related
How the assistant scrapes lists, diffs runs, and delivers files.
How approvals and questions work in chat.
Credits, step budgets, and what the assistant hands off.
The credential store behind saved logins.