DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to check a phone setting from the terminal with Artemis

Give ARTEMIS a plain-language instruction and read the result in your terminal.

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 developer who wants a quick check of app behavior on a phone without writing test code.

The problemConfirming one small screen detail, such as a battery level, means tapping through menus by hand every time.

The outcomeA structured result in the terminal that says whether the task succeeded and what the device showed.

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

  1. Run git clone https://github.com/google/artemis.git && cd artemis
  2. Connect an Android device with USB Debugging enabled, or start an emulator.
  3. Run ./start.sh on macOS or Linux, or .\start.bat in Windows PowerShell, to install the toolchain.
  4. Run uv run artemis run "Open Settings, find Battery and tell me current level" --profile flash
  5. Read the structured terminal output and confirm the reported battery level matches the device screen.

Prompt for your agent

In the google/artemis repo, run `uv run artemis run "<instruction>" --profile flash` against the connected device. Expected output: a structured terminal result with a success or failure status and the value the device showed. Verify the reported value matches the on-screen value.

Caveat. The README describes the flash profile as best for routine, deterministic UI tasks, so open-ended exploration is better handled with the pro profile.

Share: 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