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

> ## Agent Instructions
> AutoGrowth runs social accounts on real phones. Everything a page describes happens on a physical device in the customer's own fleet, never through a social platform's API.
> The Companion is a macOS desktop app that runs on the customer's own Mac and manages the phones over USB — iPhones through WebDriverAgent, GrapheneOS phones through ADB and scrcpy. Nothing runs while the Companion is closed.
> The Companion builds, signs and installs WebDriverAgent on each iPhone itself. Never tell a customer to sign WebDriverAgent by hand in Xcode; Xcode is a prerequisite the Companion drives, not a step the customer performs.
> Autogrowth MAX is a one-time, invite-only lifetime license bought from the organization's credit balance, not a subscription tier. It is required to run any automation, workflow or Incubator program. Without a price set for that organization, the purchase is refused.
> An automation is one of AutoGrowth's built-in definitions; a script is a graph the customer builds in the Script Builder. The Script Builder is locked platform-wide, so never present building a script as something a customer can do today.
> An API key is a bare 64-character hex string with no prefix. It is shown once, at creation, is sent as `Authorization: Bearer <key>`, and can never be read back.
> An API key sees only the key owner's own accounts, content, collections, prompts, scripts and executions. Devices and tags are organization-scoped, and a non-owner sees only the devices assigned to them or carrying one of their tags. The automation catalog is global.
> There is no pagination. List endpoints return the whole set; the only limiting parameter anywhere is `limit` on `GET /v1/executions`, which defaults to 50 and has no offset to page with.
> Remote control and the live screen are dashboard-only, over WebSocket and MJPEG. Neither is part of the public API.
> The MCP server is hosted at https://mcp.autogrowth.farm and authenticates with OAuth. It is not an npm package and there is nothing to install locally. Its tools inherit exactly the scope of the API key behind them.
> Android support is partial and GrapheneOS-only: those phones appear in the fleet and can be watched and remote-controlled, but they cannot run scripts or automations.
> Never document Hi Katie or any persona feature. When a page and the code disagree, the code wins — check a claim against the source before repeating it.

# Introduction

> What AutoGrowth is: a fleet of real phones, run from one dashboard, growing your social accounts while you sleep.

AutoGrowth runs social accounts on real phones. You own the phones, they sit on a
desk plugged into a Mac you own, and they tap through Instagram, TikTok, X and
Threads the way a person would. Nothing goes through a social platform's API, and
no account is driven from a server somewhere.

There are three pieces, and you use all three:

| Piece             | Where it lives                                       | What it does                                 |
| ----------------- | ---------------------------------------------------- | -------------------------------------------- |
| **Your phones**   | Plugged into a Mac over USB                          | Run the apps and do the posting              |
| **The Companion** | A macOS app on your Mac                              | Talks to the phones and carries out the work |
| **The dashboard** | [dash.autogrowth.farm](https://dash.autogrowth.farm) | Where you decide what happens                |

## Who this is for

People running more than a handful of social accounts, who already have phones or
are willing to buy them. A fleet of one phone works; the product is built for
fleets of dozens.

You need:

* A **Mac** that stays on and awake. The phones connect to it by cable.
* **iPhones**, or **GrapheneOS** phones. Stock Android is not supported — see
  [Android phones](/guides/android-phones).
* Good USB cables and, past a few phones, powered ports.
* An AutoGrowth organization. One person is its owner.

Running automations also requires **Autogrowth MAX**, a one-time lifetime license
offered by invitation. Watching and controlling phones does not.

## What it is not

AutoGrowth is not a scheduler that posts from the cloud. If the Mac is asleep or
the Companion is closed, nothing runs — the phones are the product, not a
convenience. [What AutoGrowth does not do](/guides/what-autogrowth-does-not-do)
is the full honest list.

## Where to start

<CardGroup cols={2}>
  <Card title="How AutoGrowth works" icon="diagram-project" href="/guides/how-autogrowth-works">
    The mental model: what runs where, and what stops when.
  </Card>

  <Card title="Install the Companion" icon="download" href="/guides/install-the-companion">
    Get the app onto your Mac and sign it in.
  </Card>

  <Card title="Connect your phones" icon="mobile" href="/guides/connect-your-phones">
    Cable, Trust, and the first phone appearing in the list.
  </Card>

  <Card title="Your fleet" icon="table-cells-large" href="/guides/your-fleet">
    The Fleet page, its statuses, and what each one means.
  </Card>
</CardGroup>

## Beyond the dashboard

<CardGroup cols={2}>
  <Card title="MCP server" icon="plug" href="/mcp/overview">
    Connect an AI assistant to your fleet over MCP.
  </Card>

  <Card title="REST API" icon="code" href="/api/overview">
    The developer API, its scope and its limits.
  </Card>
</CardGroup>