Authorization notice. Artemis is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Who it is forA QA engineer preparing a shared test phone before a batch of automated runs.
The problemThe first task on a device waits about 3 seconds while the helper installs, and a failing helper can disrupt a run mid-task.
The outcomeA device with the helper installed and a diagnostic report showing whether ARTEMIS can drive it.
What you need first
- An Android device with USB Debugging enabled, or a running emulator
- git and a terminal (macOS, Linux, or Windows PowerShell)
- uv and Python, which the start script can install for you
- An AI IDE such as Antigravity, Codex, or Claude Code, if you want MCP control
Steps
- Connect the Android device with USB Debugging enabled, or start an emulator.
- Run
uv run artemis helper installto pre-install the helper. - Run
uv run artemis helper statusto confirm the helper is installed. - Run
uv run artemis doctorand review the report for any problems. - If you do not want the helper, set
ARTEMIS_HELPER_AUTO_INSTALL=falsein.envor useARTEMIS_HIERARCHY_BACKEND=uiautomator.
Prompt for your agent
In the google/artemis repo, run `uv run artemis helper install`, then `uv run artemis helper status`, then `uv run artemis doctor` against the connected device. Expected output: the helper status and the doctor report. Verify that the helper is listed as installed before any test task is started.
Caveat. The helper is an accessibility service that reads the screen layout, so a user should review the notice and Settings > Accessibility entry on the phone before installing it.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page