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

# Phone Setup

> Prepare an Android device for the agent: install, permissions, connection.

One phone, four steps. Once the device reports **Connected**, every MCP client you attach can see and operate it.

<Steps>
  <Step title="Install and sign in">
    Install the **AGI Android app** and sign in with the same account you use
    on the [AGI platform](https://platform.agi.tech).

    <Warning>
      The account must match the one your MCP client authenticates as (via
      OAuth or API key). A mismatch is the most common cause of an empty
      device list.
    </Warning>
  </Step>

  <Step title="Grant permissions">
    The app walks you through both required grants:

    * **Accessibility** - how the agent reads the screen and acts. Can also be
      enabled any time under Android **Settings > Accessibility**.
    * **Overlay** - lets the app display over other apps while a task runs.
  </Step>

  <Step title="Connect the device">
    Open **Settings > Developer connection** in the AGI Android app. Connect
    or refresh the device, then confirm the page reports **Connected**. Use
    **Refresh** whenever the connection goes stale.
  </Step>

  <Step title="Verify from your client">
    Ask your assistant to list devices, or have it call
    [`list_devices`](/api-reference/tools/list-devices) - the phone should
    appear with `status: "online"`. Not there? Run through
    [Devices & Connectivity](/guides/troubleshooting/devices).
  </Step>
</Steps>

## Managing devices

### Multiple phones

Register as many devices as you like - each is its own execution lane (one task at a time). Pick the phone that tools target when `device_id` is omitted with [`set_default_device`](/api-reference/tools/set-default-device):

* The default is persistent until changed.
* Changing it never reroutes existing work - sessions and tasks stay bound to
  the device they started on.
* For parallel workflows, use one device per workflow.

### Pausing a device

[`phone_device_pause`](/api-reference/tools/phone-device-pause) is a one-call kill switch for **new** work: tasks are rejected with `device_paused` until you call [`phone_device_resume`](/api-reference/tools/phone-device-resume). In-flight tasks keep running - cancel them separately if needed.

Useful for test devices whose state must not be disturbed, or any phone that should temporarily stop accepting automation.

### Checking health

* [`phone_device_status`](/api-reference/tools/phone-device-status) - online,
  paused, app version, `last_seen`. The quick pre-flight check.
* [`phone_get_state`](/api-reference/tools/phone-get-state) - full read-only
  snapshot: battery, network, locale, accessibility status, current app,
  launchable apps. No extra permissions needed.

<Note>
  Keep the AGI Android app updated - the tool list your MCP clients see
  depends on what the app version advertises.
</Note>

## Next

<CardGroup cols={2}>
  <Card title="Connect your AI client" icon="plug" href="/android-mcp/connect">
    Attach Claude Code, Claude Desktop, Cursor, ChatGPT, or any MCP client
  </Card>

  <Card title="Troubleshooting: devices" icon="wrench" href="/guides/troubleshooting/devices">
    Missing devices, offline devices, short tool lists
  </Card>
</CardGroup>