Coding agents in cloud sandboxes can’t run an Android emulator.
The emulator needs hardware virtualization (KVM), and cloud sandboxes don’t have it. Developers write that into the files their coding agents read. Here are 24 of those lines, word for word, each linked to where it stands.
Quoted from public AGENTS.md and CLAUDE.md files, read . Their authors aren’t affiliated with Mobilebox.
No KVM, so no emulator
Cloud sandboxes rarely expose hardware virtualization, and the Android emulator needs it.
mariuz/castle-doom · CLAUDE.md L72–73there is no emulator here (no KVM), so it is only run on real devices.
Seafloor-Studio/newspaperss · CLAUDE.md L38There is no emulator there (no KVM): device tests run in CI.
crockalet/haunt · CLAUDE.md L33No KVM in the cloud container, so no emulator; verify with unit tests and the JVM screenshot tests
tag1consulting/lagoon-app · CLAUDE.md L156There is no
/dev/kvmand no virtualization CPU flags, so the Android emulator cannot run — this one is hardware, not policy.
abhiabhi94/arrow-game · CLAUDE.md L122Claude Code on the web has no Android emulator (no KVM).
amirmohebalinezhad/Kheyr · AGENTS.md L35–36the Android emulator cannot boot and the app cannot be launched with a UI here.
jamesleekko/ZB_Canteen · AGENTS.md L26The Android emulator requires KVM hardware acceleration, which is unavailable in the Firecracker-based Cloud Agent environment.
patrickrb/sstvaf · AGENTS.md L29Orbs have no KVM: do not install/start Android emulators.
The emulator is too slow
Without KVM it runs in software: boots take minutes and every step crawls.
snonux/comicredr · AGENTS.md L337–338The emulator has no KVM there, so a page takes about 13 minutes to detect (0.2 s natively)
danielphingston/metro-launcher · CLAUDE.md L61Boot takes 10 to 15 minutes; wait for
adb shell getprop sys.boot_completedto print 1, then another minute.
Vitorr32/umavpn-connect · AGENTS.md L49Cloud VMs typically lack
/dev/kvm, so the emulator runs in software mode and boots very slowly (10+ minutes).
BenItBuhner/Cesium · AGENTS.md L92–93Expect a slow boot (~10 min) and a sluggish but usable guest.
Sabeel-Institute/sabeel-institute-kanban · CLAUDE.md L775–776On an unaccelerated host expect several minutes to boot and ~14 s per screenshot
ahmedsaed/Peace · AGENTS.md L237–238Maestro does not run on every push — it needs a booted emulator, which is minutes rather than seconds.
khaidarsafarov-droid/MyFinance · AGENTS.md L52–53adb shell input textdrops characters on the slow emulator
pepper-candy/NotiGuard_RAISE · AGENTS.md L31–32UI interactions can trigger a spurious "isn't responding" (ANR) dialog — this is emulation slowness, not an app bug.
Nothing to test on
Reviews ask for evidence from a running app, and the agent has no phone to get it.
PocketShell-io/pocketshell · AGENTS.md L57User-facing Android/terminal/SSH/tmux/agent/setup/release-gate work needs reviewer emulator evidence
jesserockz/little-videos · AGENTS.md L36–37Any PR that adds or changes UI must include screenshots and a screen recording of the change running on a device or emulator
cobarx/pubnet-tools · CLAUDE.md L199–200On-device / emulator runs are not covered by the dev container (no adb device, no KVM).
thekorn/network-audit · AGENTS.md L14–15If it is unavailable, report the blocker rather than trying to emulate inside the orb.
joemast/shared-shopping-list-mobile · AGENTS.md L42Docker Desktop on macOS has no KVM, so a local run is unsupported — not a skipped pass.
Black frames
When it does run, the screenshot an agent checks can come back black.
snonux/comicredr · AGENTS.md L343–345The same emulator draws nothing but black for a Flutter app on Impeller (the default) with
-gpu swiftshader_indirect: frames are made, the screenshot is black.
sal0-h/charuco-calibrator-android · AGENTS.md L34–35The display frequently fails to composite (screencap returns an all-black frame).
snonux/comicredr · AGENTS.md L340–341On that emulator every PNG fails to decode, in any Flutter app
A phone instead of an emulator.
Mobilebox gives your agent a cloud Android phone over MCP: ready in 19.4 s in our November 2026 benchmark, $0.01 a minute. Your agent installs the build, walks the flow and screenshots it, from inside the same cloud sandbox.
- 1
Add the MCP server
One URL,
https://mobilebox.dev/mcp, in Claude Code, Codex, Cursor or any MCP client. - 2
The agent starts a phone
It installs your APK and reads the screen as numbered elements.
- 3
It checks the flow
Taps, types, takes screenshots for the pull request, then deletes the phone.
Read more
No KVM in CI? Run the APK on a remote Android phone
Why the Android emulator stalls without KVM, three ways around it, and a tested curl script that installs an APK on a cloud phone from any runner.
Test your Android app with Claude Code on a cloud phone
Give Claude Code a hosted Android phone over MCP, install your APK from a URL, check the first screen and delete the phone, with the tool calls we ran.
Screenshots in every pull request: let your agent test the app on its own phone
Each agent on a PR starts a cloud Android phone, installs the build, walks the flow and posts a proof comment with screenshots, time and cost. The GitHub Action, the MCP prompt, before and after, and what is kept.