Isolated cloud Androids for parallel agent jobs

Shared emulators leak identity across jobs: one fingerprint, one IP, one process that dies when the laptop sleeps. Parallel agent work needs separation.
I kept hitting the same wall last month. I'd spin up three jobs on one Android emulator, grab coffee, and come back to a mess. The laptop had slept. The process was gone. Worse, job two had inherited job one's login cookie because they shared a profile folder. That's not a lab. That's a pile-up.
FoxPhone is a cloud phone platform: isolated Android devices with their own fingerprints and networks, Android 10-15 on ARM, driven from a browser. Agents can install apps and walk flows across a fleet; one-click sync helps when a human needs a master window. Pricing is usage-based with a free trial.
What I actually wanted was boring reliability. A phone that stays on when my lid shuts. A second phone that doesn't know the first phone exists. A third one I can throw away after a test without wiping my desk.
Here's the picture I use when I explain it to a teammate. Think of a drawer of cheap handsets, except the drawer lives in a rack and you open each handset in a tab. You tap, you type, you install a build, you watch the screen. When the run finishes you don't hunt for a cable. You just stop that device.
People ask why not keep using the emulator that already ships with Android Studio. I still do, for layout tweaks. Emulators are fine when you're one person and one session. They fall over when five jobs start together, or when a script needs a clean advertising id, or when the machine hibernates mid-run. I've lost overnight batches to a lid I closed without thinking.
Cloud Androids aren't magic and I don't pretend they replace a handset in my pocket. Radio, camera, and sensors that depend on a real room still belong on hardware I can hold. The cloud box is for the other pile of work: sign-up flows, regression passes, account setups I don't want mixed together.
A few notes from running this way.Jobs don't share a fingerprint, so a ban or a captcha on one device stays on that device.Each device gets its own network path, which matters when a site keys off the IP.The browser is the remote. I don't install a desktop client just to poke a screen.Android versions from 10 through 15 cover most of the apps I still have to support.ARM images behave closer to phones people actually buy than an old x86 image did.If a human has to jump in, one-click sync puts their view on the same device the agent was driving.You pay for time you use. A short trial is enough to see whether a flow even survives off a laptop.
I still keep two physical phones in a drawer for photos and for anything that needs a SIM. Everything else, the disposable stuff, goes to a cloud Android I can delete on Friday.
If your agents are still sharing one emulator window, split them. One job, one device, then shut the extra ones down when you're done. That's the whole trick. It isn't glamorous. It just stops yesterday's session from leaking into today's.