If your agent runs on your own laptop and the laptop has hardware acceleration, a local Android emulator is free and fast enough. Mobilebox runs cloud Android phones for AI agents at $0.01 a minute, ready for a first screenshot in 19.4 s in our November 2026 benchmark, for agents that run somewhere without acceleration: a cloud coding agent, a CI runner without KVM, a server running many agents at once, or any run that should find the last run’s logins still there.
Sources reviewed on November 8, 2026: Android emulator acceleration, mobile-mcp and the android-emulator-runner action.
Measured timings: /benchmarks.
When the local emulator is the right call
The Android Emulator needs hardware virtualization: KVM on Linux, the Hypervisor Framework on macOS, and WHPX or AEHD on Windows. With it, a developer machine runs one or two emulators comfortably. A local MCP server such as mobile-mcp connects your agent to it over ADB. You pay nothing per minute, and you see the window.
Where it stops working
- Cloud agents. Codex cloud tasks, Claude Code on the web, Cursor background agents and most hosted agents run in Linux containers without nested virtualization or a display. There is no emulator to start, but there is a network, so an MCP URL works.
- CI. Many runners have no KVM, and the emulator then won’t boot or crawls. The no-KVM guide has a curl script that installs the APK on a cloud phone from any runner.
- Many phones. Each emulator takes several gigabytes of memory and CPU cores. Running 20 agents side by side means 20 phones, which a laptop can’t hold and a cloud account creates with 20 calls; see phones in parallel.
- State between runs. A local emulator keeps state only on that machine. A parked Mobilebox phone keeps apps, data and logins for whichever agent picks it up next, and costs nothing while parked.
Side by side
| Local emulator | Mobilebox phone | |
|---|---|---|
| Needs | Hardware acceleration, RAM, a desktop | An HTTPS connection and an API key, or MCP sign-in |
| Agent connection | Local MCP server over ADB | Hosted MCP server or REST |
| Cost | Your machine | $0.01 per phone-minute, billed per second; parked free |
| Devices | Android images; iOS Simulator on a Mac | Cloud Android, iPhone and iPad, real Android devices |
| Many at once | As many as the machine holds | One create call each |
Many teams keep the emulator for hands-on work and point the agents that run unattended at a cloud phone. Both speak MCP, so the agent’s prompt stays the same.