Routine Builder
Order active-catalogue actions and expose supported settings, cadence and assignment without editing scripts.
THE CUSTOMER COMMAND CENTRE
Operate the fleet.
Inspect the outcome.
Farms, routines, schedules, activity, evidence, health and migration belong in one operational surface. The interface is designed to answer “what needs attention?” before it asks you to run anything.
- 1Fleet size and readinessUnderstand capacity before starting more work.
- 2Currently active farmsSee execution without opening every emulator.
- 3Attention queueFailures and uncertainty stay visible.
- 4Next eligible scheduleKnow what is due and what is merely queued.
- 5Recent classified outcomesCompleted and no-action remain distinct.
USE THE PRODUCT BEFORE INSTALLING IT
Five actual customer
surfaces to inspect.
Switch views, open the full capture and read the customer decisions each screen exposes.
01 / ACTUAL CUSTOMER INTERFACE
Command overview
Fleet readiness, currently running work, the next schedule, recent outcomes and attention states in one customer surface.
- 1Fleet-wide readiness
- 2Running farms
- 3Needs-attention count
- 4Next scheduled routine
- 5Recent outcome feed
Actual development-build customer captures from September 2026. Example account state; not a live feed or reliability proof.
THE OPERATIONS LOOP
Eight surfaces.
One source of attention.
The screenshots above are the current public captures. These cards describe the additional customer surfaces present in the development interface without pretending they are new screenshots.
Schedule
See which routines are assigned, when they become eligible and which farms are waiting for capacity.
Activity
Read the ordered customer-visible stream instead of digging through a raw log file.
Evidence
Inspect outcomes, timestamps, failure context and relevant captures across the fleet.
Reports
Break executions into performed, no-action, game-block and failed outcomes—never one inflated success number.
Reliability
See bounded retries, circuit state and attention without silently forcing another attempt.
Environment Health
Separate Windows, service and emulator problems from automation results.
Migration
Preview, review and deliberately import supported GnBots configuration.
THE EVERYDAY FLOW
Choose. Configure.
Run on your terms.
You should not need to edit automation code to operate a farm.
1. Choose your farms
Select the exact LDPlayer profiles. Farms can keep different assigned routines.
2. Build the routine
Pick active actions, arrange order and set customer-facing limits.
3. Run or schedule
Start deliberately or set a cadence, then follow outcomes and evidence.
THE MEMORABLE PART
Evidence is a product surface.
See the outcome language, retry decision and customer-visible record that sit behind a result.