Google lets AI coding agents take the wheel on Android
Google just open-sourced ARTEMIS, an automation framework that lets coding assistants like Claude Code, Cursor, and Codex drive real Android devices or emulators via MCP. It runs cross-app workflows, grabs logcat crashes and screenshots, and scores a 99%+ success rate on AndroidWorld.
ARTEMIS is an open-source Android automation framework from Google that translates plain natural language into reliable actions on physical phones and emulators. Basically, it gives coding agents like Claude Code, Cursor, Codex, and Antigravity actual hands to drive connected devices, reproduce bugs, and pull crash logs while you code.
On Google Research's AndroidWorld benchmark, which spans more than 20 apps and over 100 multi-step tasks, ARTEMIS notched a 99%+ task completion rate.
What it actually does
Mobile testing usually bogs down in the tedious manual loop of compiling an APK, tapping through seven screens to reproduce a glitch, and digging through Logcat in the terminal. ARTEMIS hands all of that over to your IDE's agent.
You can give your coding assistant a single prompt: build the latest branch, install it on the tethered phone, log in with a test account, check if an error banner pops up, and send back screenshots. The agent talks to ARTEMIS over the Model Context Protocol (MCP) and drives the phone natively.
It handles cross-app workflows with ease and can run autonomous exploratory stability sessions for over 10 hours straight.
Under the hood, ARTEMIS operates in two profiles. The Flash profile is a reactive loop built for simple, deterministic workflows, executing actions in roughly 3 to 5 seconds per step. The Pro profile deploys a multi-agent graph with deep planning, taking 15 to 40 seconds per step to verify every screen target before tapping, which is ideal for thorny edge cases.
To find buttons, it reads the accessibility tree by default. If it runs into custom Flutter, Compose, or Canvas interfaces where standard node trees fail, it gracefully falls back to OCR and visual models.
How to get it running
The project is fully open source in Google's GitHub repository, shipping with native MCP server support, a Python SDK, a CLI, and a browser-based dashboard.
You just need a local machine and an Android phone with USB Debugging enabled, or a standard emulator.
Clone the repository and run ./start.sh on macOS/Linux, or start.bat on Windows. The installer handles toolchains automatically, pulling down ADB, scrcpy, FFmpeg, and uv dependencies, while mounting global MCP configurations directly into your supported AI IDEs.
Once live, it serves a visual console at localhost:8000 featuring real-time device mirroring, a prompt sandbox, and step-by-step trace replays. Python developers can also install artemis-client via uv and plug strongly typed assertions straight into pytest or existing CI/CD pipelines.
Why it matters
If you build or test Android apps, ARTEMIS is worth taking for a spin immediately. Traditional Appium scripts break the second a UI layout shifts, while pure vision-only agents are painfully sluggish and prone to hallucinated clicks. Google struck a smart balance here by marrying element trees with vision fallbacks, and plugging the whole thing into standard MCP interfaces.
The catch is operational overhead. The deep reasoning Pro profile takes up to 40 seconds a turn and will chew through model tokens quickly. It also installs a lightweight helper accessibility service on the target device, which might need extra permissions depending on your OEM ROM. Still, letting a coding agent autonomously build, tap, and diagnose on physical hardware closes a massive loop in software development.
Sources (1)
- github.com(opens in a new tab)Originalgithub.com