Android emulator for AI agents: browser-based setup guide

An AI coding agent can attach to an Android emulator for AI agents through Limrun, a cloud device layer that plugs into the Linux sandbox already in use. The agent creates and drives the emulator over MCP or the lim CLI without installing a local Android SDK or emulator, and an ADB tunnel for local tools needs only adb from Platform-Tools. Instead of adding hardware or a second platform, the team gives its existing agent a remote device target that it can build, test, and share from the same workflow. This guide covers the connection paths, the service model, browser access, and the CI setup.

How do I give an AI agent an Android emulator?

Give the agent a device-control interface that can create and drive a remote device. Limrun opens that path through an MCP server, a link scoped to each instance, CLI skills, and SDKs, so the agent never installs an Android SDK locally. That setup matters because coding agents increasingly act on their own.

The platform's mobile simulator MCP guide walks through the tool set for creating instances and driving devices. The server has 16 tools for instance creation and device control. It lives at https://mcp.limrun.com/mcp and installs from the Claude connectors directory, the ChatGPT plugin, or the Limrun plugin for Claude Code, Codex CLI, Gemini CLI, and Cursor.

For this workflow, the Android emulator runs Android 14 and 15 and can be controlled through the lim CLI, the TypeScript SDK, or MCP, or over an ADB tunnel. That remote Android emulator setup removes the SDK install from the agent's environment and keeps device state in one place. An Android emulator for AI agents therefore follows one rule: the agent owns the control path, while the platform owns the device runtime.

What does Android emulator as a service provide?

Android emulator as a service supplies a device over the network instead of on a developer laptop. The service removes the toolchain setup from local machines and runs the emulator while the team pays for usage rather than owned hardware. That shifts maintenance and cost to the provider.

Remote Gradle builds on Limrun detect React Native and Expo projects automatically, so an agent can submit a repo and reach a build without preinstalling toolchains. The remote Android emulator guide lists the instance creation steps and SDK calls for starting a device.

Limrun offers usage-based, monthly, and annual plans, listed on the pricing page, and new accounts sign up free with trial credits.

Can I run an Android emulator in the browser?

Yes. A browser-based Android emulator streams the live device into a web page, so reviewers and teammates can tap and watch without installing anything. Every running Limrun emulator has a signed stream URL that opens in any browser with no Limrun sign-in, and lim android create opens it for you. This makes review possible without installing the app or the emulator locally.

Anyone with that link can watch and control the same emulator the agent uses while the instance runs, so share it only with people who should have access. The live simulator embed component lets a product put the emulator directly in a web page, and the tokens only work for that one instance.

From the same workflow, the agent can record a video of the run (lim android record start, then stop), and the team can publish the build to a Google Play testing track to check it on real phones. A browser-based Android emulator for AI agents is useful after the agent finishes a change; the reviewer checks the same state the agent produced. The device itself stays in the cloud, so nobody has to download an APK to understand the current build.

How does an ADB tunnel for Android emulators work?

An ADB tunnel on Limrun forwards the Android Debug Bridge protocol from a cloud device to local tools. Android Studio, scrcpy, and Appium can then treat the remote emulator like a locally connected device while the Android runtime stays in the cloud.

lim android connect opens that tunnel, and lim android create opens it by default. Through it, a developer can pick the emulator in Android Studio's device selector with no port to set, mirror the screen with scrcpy, or run Appium tests against the same remote instance.

Teams can also pin an emulator instance to the US, EU, or Asia from the CLI, the TypeScript SDK, or the REST API, or place it near the end user from an SDK. The MCP tools do not set region. The closer region shortens the command and frame path for interactive work. For an Android emulator for AI agents, this tunnel keeps the agent's tooling unchanged. The agent still issues ADB commands, but it does not need to locate or manage a physical device.

How does a cloud Android emulator for agents fit into CI?

A cloud Android emulator for agents becomes the device target in pull request checks. The CI job or agent builds against the remote emulator, installs the APK, runs tests, and shares a link. The runner needs no Android SDK for the Gradle build, and Appium tests need adb on the runner, which GitHub's ubuntu-latest image already ships.

A code review loop still needs a runtime check before merge. An agent that can open a review and then drive an emulator closes that gap in one workflow.

The platform works with Appium on Android and Playwright on Android Chrome, so tests can cover both native UI and web content in the same device. Appium runs on your side with an upstream driver such as UiAutomator2 and reaches the emulator through the ADB tunnel. The platform can also publish the signed build to Google Play once tests pass. For an Android emulator for AI agents, CI is where the device becomes part of the merge decision.

How do I set it up?

Connect the agent over MCP or install the lim CLI, then share the stream link with reviewers. The Run an emulator guide covers the create options and the ADB tunnel.

1. Connect the agent. In Claude Code, run /plugin marketplace add limrun-inc/skills, then /plugin install limrun@limrun. The MCP guide lists the plugin installs for Codex CLI, Gemini CLI, and Cursor. Any other client connects to https://mcp.limrun.com/mcp and signs in with OAuth, or sends an API key in an Authorization: Bearer header for headless agents.
2. Or work from a shell. Run npm install --global lim, then lim login, then lim android create. It boots the emulator, opens the ADB tunnel (which needs adb; pass --no-connect to skip it), and prints the signed stream URL.
3. Share the signed stream URL with reviewers. Anyone with the link can control the device while it runs, so share it only with people who should have access.
4. For pull requests, add limrun-inc/android-preview-action. It builds the APK on a Gradle sandbox and posts a preview link that members of your Limrun organization can open.

FAQ

Which Android versions does the cloud emulator support?

The platform's Android emulator runs Android 14 and 15. Teams can choose between the two from the CLI or an SDK. The emulator is controlled through the lim CLI, the TypeScript SDK, or MCP, or over an ADB tunnel, and the same instance can stay pinned to the selected region.

How do I connect Android Studio or scrcpy to the emulator?

The ADB tunnel, opened by lim android connect or lim android create, forwards the connection to local tools. While it runs, the emulator appears in Android Studio's device selector, and scrcpy can mirror the screen. Appium can use the same path for UI automation.

How does a coding agent create a new cloud emulator instance?

A coding agent creates an instance through the platform's MCP server, the CLI, or an SDK. The MCP server includes 16 tools for instance creation and device control. The remote MCP server at https://mcp.limrun.com/mcp installs from the Claude connectors directory, the ChatGPT plugin, or the Limrun plugin for Claude Code, Codex CLI, Gemini CLI, and Cursor.

How does CI install an APK on the emulator?

A CI job can let the platform's Gradle support build the APK and install it on the emulator. The Gradle build needs no Android SDK, JDK, or keystore on the runner. Tests can then run through Appium, which needs adb on the runner's PATH, or Playwright, which needs only Node and the playwright package.

How do teammates view the same running emulator?

Teammates open the instance's signed stream URL in any browser, with no Limrun sign-in. They can tap and watch the running app without installing anything while the instance runs, and anyone with the link can control the device, so share it only with people who should have access. A React embed component can place the live simulator in a web page with tokens scoped to that instance.

What Android testing frameworks can run on the emulator?

The platform works with Appium on Android, which you run with an upstream driver such as UiAutomator2 over the ADB tunnel, and with Playwright on Android Chrome. Teams can also connect scrcpy or Android Studio through the ADB tunnel. That covers UI testing, web content checks, and manual inspection from the same remote device.

What does the platform charge for Android emulator usage?

Plans are usage-based, monthly, or annual. New accounts sign up free with trial credits, and current plans are on the pricing page.

Is region pinning available for an emulator instance?

Yes. Teams can pin an instance to the US, EU, or Asia from the CLI, the TypeScript SDK, or the REST API, or place it near the end user from an SDK. The MCP tools do not set region. Choosing a nearby region reduces latency for interactive sessions and keeps the emulator closer to the people checking the app.

Sign up free in the Limrun console, create an Android emulator for AI agents, and connect your agent through the MCP guide in about three minutes.