Documentation

Getting Started

Pandora Hub controls a fleet of rooted Android cloud phones that each run several Roblox clones for automated farming. You manage the whole fleet from one dashboard.

1. Open the panel and Sign in with Discord.
2. Redeem a license key to unlock devices and script slots (see below).
3. Install the Pandora agent on each cloud phone — it auto-enrolls into your fleet.
4. Add your Roblox accounts in the Cookie Manager and assign them to device slots.
5. Press Start on a device — it launches, signs in, and joins each clone into the game.

License & Plans

Access is metered two ways, redeemed with keys on the Redeem page:

Device license

Grants a number of devices for a fixed window (e.g. N devices × up to 10 clones each × 30 days). Your device allowance stacks when you redeem more keys.

Script slots

Paid scripts (Grow a Garden 2) are metered per Roblox username. Each script slot lets one account run the paid script; the free tracker doesn't use slots.

Your Fleet (Devices)

A device is one cloud phone running the Pandora agent. The Devices page shows every device as a card with its live status.

Enrolling a device

1. On the device page, download the agent APK for your account (it's stamped with your enroll token).
2. Install it on the cloud phone and grant root. It connects and appears in your fleet within seconds.
3. Rename it (e.g. FARM-1) so it's easy to find.

Reading a device card

Each card shows: Online/Offline, Idle or Monitoring, number of packages (clones), live CPU / RAM, and an X/Y run counter (X clones actually in-game out of Y configured). Sort and search the list from the top bar — your sort choice is remembered.

Running Bots

Start / Stop / Rejoin

Start launches every assigned clone, signs it in with its cookie, and joins it into the server. Stop closes them. Rejoin re-sends the join without a full relaunch.

Auto Grid (window tiling)

Clones open as floating windows. Pick a grid preset (e.g. 2×5 or 3×4 for ten clones) so every window tiles neatly and you can watch them all at once.

Launch Delay

Bots launch one at a time with a stagger (default 90s, min 30s) so many joins from one datacenter IP don't trip Roblox rate-limiting (HTTP 529). Lower it only if your IPs can take it.

Cookie Manager (Accounts)

An account is one .ROBLOSECURITY cookie. The Accounts page is your Cookie Manager.

Adding accounts

1. Click Add and paste one or many cookies (one per line) — they're bulk-imported.
2. Each is validated against Roblox; the resolved username and avatar are saved.
3. Cookies are encrypted at rest and never shown in full.

Status & filters

Every account is valid, invalid, or unchecked. Use Re-check to refresh live status. Filter the list with the chips:

1. Valid / Invalid / Unchecked — by live status.
2. Unassigned — accounts not yet assigned to any device slot.
3. Duplicates — the same Roblox username stored on more than one account, so you can clean them up.

Assigning Accounts

Each device has a fixed number of clone slots (packages). Assign an account to a slot so that clone signs in as that account.

1. Select one or more accounts (or "select all matching" a filter).
2. Click Assign, choose a device, and confirm — free slots are filled in order.
3. The Assigned column shows the device name and package, e.g. FARM-19/com.roblox.seiyy.

Press Start (or the device auto-refreshes) and the newly-assigned clones launch on their next cycle.

Scripts — Grow a Garden 2

Clones run the Grow a Garden 2 (GAG2) auto-farm. Configure it globally or per-device.

What it does

Plant, harvest, water, claim, and (optionally) buy — all automatically. Destructive features (Auto Mail, Auto Shovel, Sell) are OFF by default and only run if you explicitly enable them, so nothing is sent away or dug up by accident.

Auto-buy

Set a buy list (seeds / gears / eggs) with per-item conditions. Buying is a separate list from the feature toggles, so enabling features never means "buy everything."

Auto Recovery (VIP)

Roblox occasionally invalidates cookies. Auto Recovery re-logs dead accounts back in and replaces the dead cookie with a fresh one — no manual re-adding.

1. Store the account's password alongside its cookie (required for recovery).
2. Turn on Auto Recovery for your tenant — dead accounts are queued and re-logged automatically.
3. Recovered accounts flip back to valid and the fleet re-launches their clones.

Executors

The Executors page installs executor apps (Delta and others) to your devices straight from the panel — no manual sideloading. Pick an executor and the devices download and install it.

FAQ & Troubleshooting

A device shows Offline

The agent lost its connection. Check the cloud phone is powered on and online; it reconnects automatically. If it stays offline, reinstall the agent.

An account is Invalid

Its cookie died. Re-check it, replace the cookie in the Cookie Manager, or (VIP) let Auto Recovery re-log it. Invalid accounts are skipped at launch so they don't waste cycles.

Clones aren't joining the game

Make sure a private-server link is set, the cookie is valid, and the launch delay isn't so low that joins are rate-limited (529). The in-game detector confirms the real state on each card.

Windows aren't tiled

Set an Auto Grid preset that matches your clone count. Freshly-installed clones tile on their next launch once the agent has established them.