Practical overview
When it fits
Use ARTEMIS when a test or workflow needs to interact with Android app interfaces across multiple steps, especially when you want to drive a connected phone from a test framework, CLI or MCP-enabled development environment.
Who it is for
- Mobile QA engineers running end-to-end or exploratory tests.
- Developers integrating Android task automation into Python test suites or CI/CD pipelines.
- AI coding-assistant users who want to dispatch device tasks and inspect diagnostics through MCP.
Documented uses
- Automate multi-step workflows across Android applications from natural-language instructions.
- Run Android tests from a terminal, Python framework or the web console.
- Connect an AI IDE to a real device for test execution, bug reproduction and diagnostic collection.
- Inspect execution trajectories, replay tasks and capture logs or screenshots.
Requirements & limits
- Requires Python 3.12+ and a connected Android device with USB debugging, or an emulator.
- The repository documents setup scripts for macOS, Linux and Windows PowerShell.
- The project offers distinct CLI, web console, Python SDK and MCP routes for different development workflows.
- First device use installs an Accessibility Helper; the project documents how to inspect or uninstall it.
- The code is licensed under Apache-2.0.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up ARTEMIS on a connected Android device
Clone the repository and launch its setup flow on macOS, Linux or Windows PowerShell.
Before you start
- Python 3.12 or later, as listed by the project.
- An Android device with USB debugging enabled, or an emulator.
- Git and a terminal.
Steps
Clone https://github.com/google/artemis.git and change into the artemis directory.
On macOS or Linux, run ./start.sh. On Windows PowerShell, run .\start.bat.
Follow the setup prompts; the script detects and installs the listed system toolchains and Python dependencies, and can offer MCP and IDE-rule configuration.
Expected outcome
The project’s local interface opens in a browser with a device connection wizard, live screen mirroring, a prompt sandbox and execution replays.
Guide limitations
- The guide covers setup and launch, not a specific task execution workflow.
- A connected Android device or emulator is still required.
- The first device task installs the ARTEMIS Accessibility Helper; project instructions provide a command to remove it.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 2 October 2026
- Original website title
- google/artemis · Official homepage title · retained in its source language

