~/guides/PHONE.md

Guides / AI tools

Google’s open-source ARTEMIS lets Claude Code use your Android phone: Maps, music and a report, from one sentence

ARTEMIS, free and open-sourced by Google, lets an AI use an Android phone like a person and plugs into Claude Code. Checklist, install, first prompt, limits.

Type one sentence and the AI swipes the phone by itself: opens Maps, plans a route, then plays a song. That is the official demo of ARTEMIS, a free tool Google open-sourced on GitHub. It reads the screen, taps, types and keeps a to-do list it ticks off step by step, and it ships an MCP server, so Claude Code can plug in. The limit up front: Android phones and emulators only, no iPhone yet. This is the full version of the PHONE reel, checked against the official GitHub on 27 October 2026.

01The result first: one sentence, the phone moves by itself

Reel frame: an instruction card (plan a Maps route, then play Coldplay on YouTube) next to a phone playing Yellow
The official ARTEMIS demo: one instruction, a multi-stop Maps route, then a song on YouTube (frames from GitHub).

ARTEMIS is a free tool Google open-sourced on GitHub (Apache-2.0). It lets an AI use a real Android phone like a person: read the screen, tap buttons, type, swipe, then report back. In the official README demo, one sentence makes it plan a multi-stop driving route in Google Maps, add up the total time, then open YouTube and play Coldplay. It ships its own MCP server, so Claude Code can give it tasks directly.

In this guide you get:

  1. What it can and can’t do (up front: no iPhone yet).
  2. A 5-item checklist before you start.
  3. The install commands from the README, for Windows and Mac.
  4. How to connect it to Claude Code and what to say first.
  5. What to watch for safety.

02How ARTEMIS does it

Reel frame: the task_plan.md checklist from the ARTEMIS demo ticking off, next to a phone showing the route
It writes a to-do list first (task_plan.md) and ticks each step (official demo frames).

It reads the structure of the phone screen (which parts are buttons, which are text fields) and falls back to screenshots and a vision model when it can’t, then taps through step by step. There are two modes: Flash is fast, about 3–5 seconds a step, for simple routine actions; Pro writes a plan first, checks before every action and ends with a report, about 15–40 seconds a step, for long workflows.

AndroidWorld leaderboard: Project ARTEMIS marked OURS in first place at 99.1%, human performance 80%
The AndroidWorld leaderboard in the README: ARTEMIS reports 99.1% for itself (marked OURS).

03Before you start: these 5 things

Reel frame: checklist ticking Android phone or emulator and USB debugging, a green Android phone, USB cable
Android phones and emulators only; iPhone is on the official roadmap.
  1. An Android phone, or an Android emulator on your computer. iPhone isn’t supported yet (iOS is on the official roadmap).
  2. USB debugging on the phone: Settings → About phone → tap Build number 7 times to unlock Developer options, then turn on USB debugging (menu names vary by brand), and connect it by USB.
  3. Git on your computer. ADB, scrcpy, FFmpeg and the Python packages are installed by the start script.
  4. One AI API key: Gemini, OpenAI, Anthropic, OpenRouter or xAI; ARTEMIS uses it to understand the screen. API use is billed separately by each provider.
  5. Claude Code, if you want Claude Code to drive it.

04Install: run start once, add one key

Reel frame: terminal with git clone and start.bat, MCP connected to Claude Code, a .env card with a masked key
The README’s one-click start: it installs the tools and offers to connect Claude Code.
Windows (PowerShell)
git clone https://github.com/google/artemis.git
cd artemis
.\start.bat
Mac / Linux
git clone https://github.com/google/artemis.git && cd artemis
./start.sh
  1. The first run installs ADB, scrcpy, FFmpeg and the Python (uv) packages.
  2. It asks whether to install the MCP config and rules into your AI tools; pick Claude Code.
  3. Copy .env.example in the artemis folder to .env and add one key, for example ANTHROPIC_API_KEY=your-key.
  4. A browser opens http://localhost:8000 with a device wizard, live screen mirroring, a prompt panel and replays.
To connect Claude Code by hand later (inside the artemis folder)
uv run artemis mcp --install claude

05What to say first

Reel frame: a Claude Code card asking for the battery level, a cable to the phone labelled mobile_run_task
Just say it in Claude Code; it calls ARTEMIS’s mobile_run_task tool.

Once connected, tell Claude Code in plain words what the phone should do. Claude Code calls ARTEMIS’s MCP tools (for example mobile_run_task to run a task, mobile_get_device_state to check the phone) and returns the result with screenshots.

Start simple
On my connected Android phone: open Settings, find Battery and tell me the current level.
Next: like the official demo (replace the [ ])
On my phone: open Google Maps, plan a driving route from [the station] to [the beach] and tell me how long it takes; then open YouTube, search for [a song] and play it.
Without Claude Code, in the terminal (the README’s example)
uv run artemis run "Open Settings, find Battery and tell me current level" --profile flash

06Good to know

  1. Android only; iPhone doesn’t work yet.
  2. It really operates your phone. Don’t let it pay, delete or send anything unattended; watch it for steps you can’t undo.
  3. An API key is like a wallet: don’t paste it where others can see it, and never upload the .env file to GitHub.
  4. Turn USB debugging off when you’re done.
  5. The 99% success rate is the project’s own benchmark result; not every app will go that smoothly.
  6. Download only from the official github.com/google/artemis; don’t install look-alike repos.

Sources

Related guides