Thursday, September 10, 2026

ARTEMIS

★1,040Must watch
DemoAPIMCP

Google’s open stack so coding agents drive a real Android phone — natural language in, taps and Logcat out, MCP into your IDE.

ARTEMIS

Why it matters

ARTEMIS is Google Pixel Test Engineering’s open-source Android automation layer for AI assistants and test suites. You describe a workflow in plain language; it runs observe-and-act steps on a USB device or emulator, using UI element indices when it can and vision or coordinates when the UI is custom. It ships a local web UI with screen mirroring, a Python SDK for pytest-style runs, and a native MCP server so IDEs can call mobile tools directly. On Google Research’s AndroidWorld benchmark it reports 99%+ task success across 100+ multi-step flows.

Web agents already click browsers. Mobile still breaks most agent loops. If you ship Android, ARTEMIS lets Claude Code, Codex, or Antigravity install a build, walk the UI, grab screenshots and logs, and report failures without a hand-written Appium suite.

How it works

Clone the repo, connect a phone with USB debugging or an emulator, and run ./start.sh. It installs ADB, scrcpy, and deps, then can wire MCP plus a mobile-testing rules file into Claude Code, Codex, Cursor, Antigravity, and similar tools. From chat you ask it to build an APK, install it, walk login, and return screenshots. Or call uv run artemis run "…" from the CLI. Flash mode aims for a few seconds per step; Pro mode explores blocked paths longer before giving up.

Not another coding harness and not a browser agent. ARTEMIS is the phone side of the agent stack — real device control, MCP, and diagnostics — so mobile QA sits next to the same IDE agents you already use for code.

Capabilities

DemoAPIMCP
  • Public demo available
  • API / SDK surface
  • MCP server / client support
androidmobilemcptest-automationai-agentsgoogle
Source ↗

Via github

X