artemis
ARTEMIS turns natural-language instructions into reliable Android automation. It automates end-to-end workflows, captures logs, and integrates seamlessly with AI coding assistants such as Antigravity, Codex, and Claude Code. It also achieves 99%+ success rate on AndroidWorld Benchmark.
Runs with mockssource: GitHubPythonApache-2.0commit 371aa6df5688
Python, Apache-2.0 licensed. The project labels itself: ai agents, android, google, test automation and testing.
artemis runs, with stand-ins for the services it depends on. An Argusic agent installed it in 3 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
uv sync --dev installs cleanly; artemis doctor runs; 2185/2185 pytest suite passes with a mock API key; 3 pre-existing code and fixture bugs fixed.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- subprocess.CREATE_NEW_PROCESS_GROUP does not exist on Linux in device_utils test3 minutes
- video frame count assertion 43-47 fails; actual frames 773 minutes
- adb_server_manifest fixture descriptions mismatch MCP v1.29.0 indentation2 minutes
- Install time
- 3 minutes
- Cold machine to finish
- 26 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- uv run pytest: 2185 passed, 10 skipped, 8 deselected
- Model tokens used
- 267,259
- Exact commit tested
- 371aa6df5688
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
<pre style="background: #f0f0f0; padding: 8px;">ARGUSIC_RESULT: {"install_succeeded": true, "launch…
tokens used
267,259
All 2185 tests pass with zero failures. Here's the full report:
**Install**: `uv sync --dev` installed all 191 packages cleanly (~1m17s). The CLI binary (`uv run a…
**Errors encountered and fixed** (3):
| Error | Fix |
|---|---|
| `adb_server_manifest.json` fixture had indentation mismatched with MCP v1.29.0 docstring formatti…
| `test_ensure_emulator_uses_windows_creation_flags` failed because `subprocess.CREATE_NEW_PROCESS_…
| `test_analyzer_clip_keeps_timeline_time_across_restart_gap` produced 77 frames instead of the exp…
<pre style="background: #f0f0f0; padding: 8px;">ARGUSIC_RESULT: {"install_succeeded": true, "launch…Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 3 minutes, faster than the median of the 22 comparable projects Argusic has measured.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 23 ai-agents projects Argusic has installed and timed, artemis was the 8th fastest to reach a running state, and 14 of 23 reached one at all.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.10 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/artemis)Questions
- Does artemis run?
- artemis runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test artemis?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 371aa6df5688. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test artemis?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does artemis take to install?
- 3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does artemis need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing artemis?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does artemis compare with the alternatives?
- Of the 23 ai-agents projects Argusic has installed and timed, artemis was the 8th fastest to reach a running state, and 14 of 23 reached one at all.
- Where is the evidence for artemis?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.