What AutoGrowth does not do

Everything here is true today. None of it is hidden behind a setting you have not found.

Nothing runs while the Companion is closed

Close the Companion, put the Mac to sleep, or unplug the phones, and the fleet stops. There is no cloud fallback, no queue that drains later on our side, and no way to post from the dashboard alone.

Runs due while a phone is away stay Pending and are picked up if the phone comes back within about two hours. After that they are Skipped. A run that was in progress when the Mac dropped ends as Failed. See How AutoGrowth works.

Android phones cannot automate

GrapheneOS phones join the fleet, stream and can be driven by hand. They cannot run automations, workflows or scheduled runs at all — not on any plan. Stock Android is not supported in any form. A Samsung, or a Pixel on the factory build, is listed as unsupported and ignored. See Android phones.

The Script Builder is locked

Building your own automation as a graph is not available to anyone. The nav item carries a Soon badge, the create button is disabled, and the feature cannot even be bought: “The Script Builder is coming soon and is not available for purchase yet.” What you can run is the fixed catalog of built-in automations.

There are no cards

No credit card, no invoice, no card on file, no subscription that bills itself. Everything is paid from your organization’s credit balance, and credits are topped up with crypto — SOL, ETH, USDC and others.


Phone slots do not auto-renew	You renew them. They stop working the moment they expire, with no grace period
No refunds and no proration	Remove a slot and the time left on it is forfeited
Deleting a phone does not free its slot	The slot stays bound to that phone until it expires
Extra storage cannot be bought	20 GB comes with each active phone slot. More storage means more slots
Autogrowth MAX is invite-only	Without a price set for your organization, the upgrade is refused outright

See Billing.

X and Threads accounts are never scraped

Follower counts, growth and profile details are only ever collected for Instagram and TikTok. An X or Threads account sits on Warming permanently and never shows statistics. It can still be automated; it just is not measured. Engagement rate is not calculated for any platform. The tile exists and generally reads 0.0%. Read followers and the 14-day trend instead.

There is no automatic update

The Companion never updates itself and never offers to. When a new version is required it shows Update Required, gives you one OK button, and closes. You then install a fresh DMG from a link an owner creates. While you are signed in and working it says nothing at all about updates.

A license key cannot be moved

A Companion key locks to the first Mac that signs in with it, permanently. There is no unbind, no reset and no transfer. Moving to a new Mac means deleting the old key and creating a new one — see Install the Companion.

Other things worth knowing


Phones cannot be renamed in AutoGrowth	The name comes from the phone itself and is refreshed every time it reconnects. Rename the iPhone in iOS Settings instead
Media is single-use	A collection is a draining queue, not a playlist. Fresh media goes first and anything already posted is taken out of the pool, because reposting risks a ban. When a collection runs dry it falls back to media it has used before, and warns every time it does
There are no folders in the library	Media is organised with collections, stars and search. That is all there is
Google Drive imports are capped at 20 files	And they arrive with no collection assigned, so you have to file them afterwards
Prompts do not write your captions	Prompt templates feed the locked Script Builder. Automation captions come from what you type on the step
An account cannot be paused from the dashboard	The bulk Pause button on the accounts list does not actually pause anything. Untracking works and only untracks — nothing changes on the phone
Removing a team member deletes them	Along with their accounts, content, prompts, executions and keys. The organization’s phones are kept. It cannot be undone
There is no ownership transfer and no way to leave	The owner is set once, at signup, and a person belongs to exactly one organization
Remote control is not exclusive	Two people can open the same phone at the same time and both will be driving it. There is no “someone else is controlling this” warning
There is no screenshot or rotate button in the viewer	Landscape is detected from the video, never chosen
Remote control and the live screen are dashboard-only	Neither is part of the API or the MCP server
The API has no pagination	List endpoints return everything. The only limit anywhere is on executions

Troubleshooting

If it is a fault rather than a limit, it is probably in here.

Getting help

Where to write, and what to include.

Start here

Set up

Run your fleet

Automate

Content

Accounts

Team and billing

Good to know

What AutoGrowth does not do

Nothing runs while the Companion is closed

Android phones cannot automate

The Script Builder is locked

There are no cards

X and Threads accounts are never scraped

There is no automatic update

A license key cannot be moved

Other things worth knowing

What to read next

Troubleshooting

Getting help

​Nothing runs while the Companion is closed

​Android phones cannot automate

​The Script Builder is locked

​There are no cards

​X and Threads accounts are never scraped

​There is no automatic update

​A license key cannot be moved

​Other things worth knowing

​What to read next

Troubleshooting

Getting help

Nothing runs while the Companion is closed

Android phones cannot automate

The Script Builder is locked

There are no cards

X and Threads accounts are never scraped

There is no automatic update

A license key cannot be moved

Other things worth knowing

What to read next