TOYS13 / WORKSPACE
Overview
YOUR WORKSPACE
Automation, with visibility.
Create a bot, inspect its task queue, and manage the services behind it. Android stays private and preserves app data across container replacements.
Durable by design
Persistent folders survive container replacement. Maintain separate encrypted backups.
Recent tasks
Checking AtlasCreate or edit a bot
Enabled bots are scheduled by the controller. Android inspection requires the Android/Appium services. Posting workflows are not included.
Add an API connection
Connections are a registry, not an automatic routing change. Runtime integration URLs and secrets still require a reviewed environment configuration. Never enter tokens or passwords in URLs.
A persistent Android device.
On your own server.
ReDroid stores installed apps, app data and sessions in its dedicated Android folder. The service requires an approved Binder/privileged-container setup.
Log in to Android apps
Connect Android over your private SSH tunnel, then use scrcpy on your computer to view the screen and log in manually.
ssh -N -L 5555:127.0.0.1:5555 toys13-agent@45.129.87.22 adb connect 127.0.0.1:5555 scrcpy -s 127.0.0.1:5555
ADB and scrcpy must be installed on your computer. There is no embedded Android screen in this first version. Google Play services and app compatibility require separate verification.
First task: device inspection
The Android bot connects through Appium, opens Android Settings and records the current package/activity. It does not post, purchase, read messages or handle your credentials.
Only Toys13 services can be controlled. No arbitrary commands, image changes, container deletion or public Docker API.
Resource plan
Android and browser/AI workloads run in separate modes to fit the 7 GiB host. Start only the services you need. The broker blocks conflicting combinations.
Limits, bind mounts, images and restart policies are reviewed in Compose. The GUI cannot increase privileges or resource caps.