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

# Quickstart

> Run your first phone task in under five minutes.

Get from zero to an AI assistant operating your Android phone in four steps.

## Prerequisites

* An Android phone with the **AGI Android app** installed and signed in to your [AGI platform](https://platform.agi.tech) account
* Accessibility and overlay permissions granted (the app walks you through both)
* An MCP client: Claude Code, Claude Desktop, Cursor, ChatGPT, or any client that supports remote MCP servers

<Steps>
  <Step title="Make your phone available">
    Open **Settings > Developer connection** in the AGI Android app. Connect or
    refresh the device, then confirm the page reports **Connected**.
  </Step>

  <Step title="Connect your MCP client">
    The fastest path is Claude Code:

    ```bash theme={null}
    claude mcp add --transport http agi-devices https://api.agi.tech/v1/mcp
    ```

    Then run `/mcp` inside Claude Code and complete the browser sign-in.

    <Tip>
      Using Claude Desktop, Cursor, ChatGPT, or another client? Follow the
      client-specific setup on the
      [Connect your AI client page](/android-mcp/connect).
    </Tip>
  </Step>

  <Step title="Verify the connection">
    Ask your assistant to list your devices. It calls
    [`list_devices`](/api-reference/tools/list-devices) and should report your
    phone as `online`:

    ```json theme={null}
    {
      "account_email": "you@example.com",
      "devices": [
        {
          "device_id": "5b6dc94d-615c-461c-b829-c5839b6986e8",
          "device_name": "samsung SM-S731U1",
          "device_model": "SM-S731U1",
          "status": "online",
          "paused": false,
          "is_default": true,
          "last_seen": "2026-08-04T00:49:41Z"
        }
      ]
    }
    ```

    If the tool list only contains `list_devices` and `set_default_device`, no
    device is registered yet - see
    [Troubleshooting](/guides/troubleshooting).
  </Step>

  <Step title="Run your first task">
    Ask in plain language:

    ```text theme={null}
    Open Settings on my phone and tell me the battery percentage.
    ```

    Under the hood, your assistant:

    1. Calls [`phone_run_task`](/api-reference/tools/phone-run-task) with the
       prompt - the call returns a `task_id` immediately.
    2. Waits on [`phone_task_monitor`](/api-reference/tools/phone-task-monitor)
       until the task completes.
    3. Reads the answer from `result` when the task finishes with
       `terminal: "ok"`.

    You can watch every step happen live on the phone's screen.
  </Step>
</Steps>

## What just happened

```text theme={null}
Your MCP client                AGI cloud                 Your phone
      │                            │                          │
      │  phone_run_task(prompt)    │                          │
      ├───────────────────────────>│   queue + dispatch       │
      │        task_id             ├─────────────────────────>│
      │<───────────────────────────┤                          │
      │                            │                          │  executes with
      │  phone_task_monitor        │                          │  accessibility
      ├───────────────────────────>│    progress streamed     │  APIs
      │                            │<─────────────────────────┤
      │  status: completed,        │                          │
      │  terminal: ok, result      │                          │
      │<───────────────────────────┤                          │
```

Execution is asynchronous: `phone_run_task` never blocks on the phone, and `phone_task_monitor` is how your assistant waits for something actionable. If the monitor returns `monitor_timed_out: true`, the task is still working - call it again.

## Next steps

<CardGroup cols={2}>
  <Card title="Task lifecycle" icon="arrows-spin" href="/guides/concepts/task-lifecycle">
    States, terminal outcomes, and the monitor loop in depth
  </Card>

  <Card title="Task design" icon="pen-to-square" href="/guides/best-practices/task-design">
    Write prompts that phone agents execute reliably
  </Card>

  <Card title="Tool reference" icon="code" href="/api-reference/tools/phone-run-task">
    Every parameter, default, and outcome
  </Card>

  <Card title="Use cases" icon="lightbulb" href="/guides/use-cases/messaging">
    Messaging, daily assistant, cross-app workflows, QA
  </Card>
</CardGroup>