> ## 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 `, 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. # Getting help > Where to write, what to include, and where the logs and error messages live in the product. Email **[support@autogrowth.farm](mailto:support@autogrowth.farm)**. The Companion also links to a Discord from the bottom of its **Sprout** panel, but email is the channel that gets a written answer. ## What to include Most problems are solved in one reply if you send these four things: * **The phone's name**, exactly as it appears in the fleet. * **When it happened** — the scheduled time of the run, with your time zone. * **The exact error text.** Copy it rather than describing it. Two messages that read alike to you often mean completely different things to us. * **What you expected to happen**, in one sentence. Never send your Companion license key or an API key. We do not need either, and we will not ask for one. ## Where to find those things | What | Where it is | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Run logs and errors** | The **Logs** page in the dashboard. Each row has the run name, the phone, the scheduled time and a red error preview; **View Logs** opens the full log. A row reading **No logs** has none stored | | **What went wrong on a Mac** | The **Sprout** panel in the Companion — the mascot button in the top bar. Its **Activity** tab keeps what has failed on that Mac, with the raw message when it has no specific fix | | **A phone's current state** | The device panel on the [Fleet](/guides/your-fleet) page. The agent chip and the **Last message** row carry the Companion's own words | | **Slot and credit questions** | **Settings → Billing** | Run logs are kept for **60 days**. If you are reporting something older than that, send the details from memory and we will look from our side. A screenshot of the screen you were on is always welcome for a dashboard problem. For a phone problem, the error text is worth more than a photo of the phone. ## Before you write Two things account for most reports: * **A phone that is offline, or a run that never started.** Walk through [Troubleshooting](/guides/troubleshooting) first — the Companion being closed, the Mac asleep, or an expired slot covers a large share of these. * **Something AutoGrowth deliberately does not do.** Automations on Android, the Script Builder, and paying by card are all on the list. See [What AutoGrowth does not do](/guides/what-autogrowth-does-not-do).