> ## 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.

# Getting started

> Go from your first conversation with the assistant to your first result on a device.

This page walks you from signing in to reading your first result. It takes a few minutes.

<Steps>
  <Step title="Sign in">
    Create a free account at [cloud.mobilerun.ai](https://cloud.mobilerun.ai). No base plan is
    required, and you don't need to add a device before you start chatting.
  </Step>

  <Step title="Say hello">
    Open a new chat and say what you want to do, or just say hi. If you don't have a device yet,
    the assistant asks about that before it asks anything else. It only asks what it can't already
    see from your account, so it won't repeat a question you've already answered.
  </Step>

  <Step title="Get a phone">
    Every task runs on a device, so the assistant helps you get one if you don't have one.

    * **Personal Phone** connects a phone you already own. The assistant points you to the connect guide; eligible accounts get one slot free.
    * **Cloud Phone** is a persistent virtual device on a monthly subscription. A proxy is strongly
      recommended for account work.
    * **Pay as you go** is a temporary Cloud Phone billed per minute, for a short one-off task.

    The assistant only creates a Pay as you go device after you clearly agree to per-minute
    billing. See [Devices](/assistant/devices) and [Device Types](/device-types) for the full
    comparison.
  </Step>

  <Step title="Give it a real task">
    Describe a concrete goal instead of a vague one. "Automate my phone" is too broad; "open
    Settings and tell me the Android version" is something it can just do. See the example prompts
    below.
  </Step>

  <Step title="Read the result">
    The assistant leads with the outcome, not a play by play. It states what succeeded or failed,
    gives you the file, link, or count you asked for, and offers a next step only when a decision
    is actually needed.
  </Step>

  <Step title="Answer if it asks">
    Mid-task, the assistant sometimes pauses to ask a clarifying question or to get your approval
    before a sensitive action, like resetting a device. Answer it and the task continues. See
    [Human in the loop](/assistant/human-in-the-loop) for how these work and what happens if you
    walk away.
  </Step>
</Steps>

## Prompts to try

Copy any of these into your first chat, adjusted to your own app or site.

> Open Settings and tell me the Android version.

> Log into this app with my account and tell me my current balance.

> Scrape all attendees of this Luma event and give me a CSV.

> Check my inbox app and summarize anything unread from the last 24 hours.

> Take a screenshot of the home screen so I can see what's installed.

> Check this page every morning and tell me if the price drops.

<Tip>
  Be specific about the app, the data you want, and the format. A precise goal takes fewer steps
  to complete, and fewer steps means a cheaper run. See [Limits and costs](/assistant/limits-and-costs).
</Tip>

## Related

<CardGroup cols={2}>
  <Card title="Overview" icon="compass" href="/assistant/overview">
    What the assistant is and what it can do.
  </Card>

  <Card title="Devices" icon="smartphone" href="/assistant/devices">
    Cloud phones, pay as you go, apps, and accounts in more depth.
  </Card>

  <Card title="Human in the loop" icon="user-check" href="/assistant/human-in-the-loop">
    Questions, approvals, and coming back to a paused run.
  </Card>

  <Card title="Cloud Quickstart" icon="code" href="/cloud/quickstart">
    Run a task from the API instead of chat.
  </Card>
</CardGroup>