Google Artemis just gave AI coding assistants hands and eyes to drive real mobile hardware. Developed by Google’s PTE Fusion team and released as an open-source framework on GitHub, it bridges natural language prompts directly to physical phone actions—letting tools like Claude Code, Codex, and Antigravity tap, swipe, and type across Android applications without writing a single line of brittle test code.
⚡ Quick Answer · What Is Google Artemis?
Google Artemis is a free, open-source AI agent framework (Apache 2.0) that translates plain English commands into physical taps, scrolls, and text entry on real Android devices. Exposing mobile controls as a FastMCP server for Claude Code and IDE agents, it executes multi-step phone tasks locally via USB debugging without routing device telemetry to external servers.
When I plugged ARTEMIS into my local terminal and watched Claude Code open Google Maps, set up a turn-by-turn driving route, and then switch over to YouTube to play music completely unassisted, it became obvious that mobile testing had crossed a major threshold.
Watch the 55-second video breakdown below to see ARTEMIS driving a live Android device in real time:
Video Demo: Real-time Android app automation driven by Claude Code via the Google Artemis FastMCP bridge.
Google Artemis: Autonomous Android Agent Framework
Bridging Claude Code and IDE coding agents directly to physical mobile hardware via FastMCP with on-device privacy.
Direct Hardware Control Over ADB
Translates plain English developer prompts into real native taps, scrolls, swipes, and text input on physical Android phones without rooting or external cloud relays.
Native FastMCP Server Protocol
Exposes device-level automation tools directly into Claude Code, Codex, and Cursor via the Model Context Protocol, enabling full CLI-driven mobile testing workflows.
Visual Screen Understanding
Replaces brittle Appium coordinate locators with multimodal visual reasoning. The agent parses real-time screen captures and adapts instantly when UI layouts shift.
100% On-Device Data Privacy
All sensitive touch interactions and screen buffers are handled locally through the on-device Accessibility Helper APK. No device telemetry ever leaks to proprietary cloud silos.
Permissive Apache 2.0 Open Source
Fully open-sourced on GitHub under Apache 2.0. Bring your own LLM keys (Gemini 2.5, Claude 3.5 Sonnet, GPT-4o) with zero recurring platform subscription tax.
What Is Google Artemis and How Does It Connect to Claude Code?
Google Artemis connects terminal-based AI agents like Claude Code directly to physical Android phones through a FastMCP server protocol. Instead of requiring developers to write brittle UI locators, it inspects real-time device screen buffers, reasons over the visual hierarchy using multimodal LLMs, and executes native touch and keyboard inputs over ADB (Android Debug Bridge).
For years, automating a real smartphone required maintaining painful Appium XML selectors or Espresso tests. If a button moved 10 pixels to the left, or an unexpected permission dialog popped up, the test suite crashed.
Google Artemis solves this by treating the phone screen the exact same way a human tester does:
Google Artemis End-to-End Execution Flow
USER INPUT
Natural language task (“Order coffee in Starbucks app and send confirmation”)
MCP CLIENT
Acts as the MCP Client, decomposing instructions into discrete tool calls
FASTMCP SERVER
Local FastMCP server exposing high-level phone manipulation tools
TRANSPORT LAYER
Connects computer to phone via USB cable or local Wi-Fi TCP/IP
ON-DEVICE DAEMON
Executes taps, scrolls, gestures, and extracts UI node trees directly on-device
PHYSICAL DEVICE
Real physical device or emulator runs the app and returns visual verification
<span class="step-badge">User Input</span>
</div>
<div class="pipeline-arrow"><i class="fas fa-chevron-down"></i></div>
<div class="pipeline-step">
<div class="step-num">2</div>
<div class="step-icon-wrap"><i class="fas fa-robot"></i></div>
<div class="step-content">
<div class="step-title">Claude Code / Coding Agent</div>
<div class="step-desc">Acts as the MCP Client, decomposing instructions into discrete tool calls</div>
</div>
<span class="step-badge">MCP Client</span>
</div>
<div class="pipeline-arrow"><i class="fas fa-chevron-down"></i></div>
<div class="pipeline-step">
<div class="step-num">3</div>
<div class="step-icon-wrap"><i class="fas fa-server"></i></div>
<div class="step-content">
<div class="step-title">Google Artemis Host Runner</div>
<div class="step-desc">Local FastMCP server exposing high-level phone manipulation tools</div>
</div>
<span class="step-badge">FastMCP Server</span>
</div>
<div class="pipeline-arrow"><i class="fas fa-chevron-down"></i></div>
<div class="pipeline-step">
<div class="step-num">4</div>
<div class="step-icon-wrap"><i class="fas fa-network-wired"></i></div>
<div class="step-content">
<div class="step-title">ADB Hardware Bridge</div>
<div class="step-desc">Connects computer to phone via USB cable or local Wi-Fi TCP/IP</div>
</div>
<span class="step-badge">Transport Layer</span>
</div>
<div class="pipeline-arrow"><i class="fas fa-chevron-down"></i></div>
<div class="pipeline-step">
<div class="step-num">5</div>
<div class="step-icon-wrap"><i class="fas fa-hand-pointer"></i></div>
<div class="step-content">
<div class="step-title">Accessibility Helper APK</div>
<div class="step-desc">Executes taps, scrolls, gestures, and extracts UI node trees directly on-device</div>
</div>
<span class="step-badge">On-Device Daemon</span>
</div>
<div class="pipeline-arrow"><i class="fas fa-chevron-down"></i></div>
<div class="pipeline-step">
<div class="step-num">6</div>
<div class="step-icon-wrap"><i class="fas fa-mobile-alt"></i></div>
<div class="step-content">
<div class="step-title">Target Android App</div>
<div class="step-desc">Real physical device or emulator runs the app and returns visual verification</div>
</div>
<span class="step-badge">Physical Device</span>
</div>
</div>
