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

How to test a mobile app flow on a real phone with an agent with Phone Harness

An agent opens your app, follows a test script, and reports what the screen shows.

Who it is forA developer or QA tester who needs to check an app's sign-in or checkout flow on a real Android or iPhone when no emulator is available.

The problemManually tapping through a flow on several phones is slow, and emulators do not always match the device a user holds.

The outcomeThe agent walks through the flow, reads the screen after each tap, and returns a step-by-step log with the final state.

What you need first

  • uv installed, with Python 3.12 available
  • A coding agent such as Claude Code or Codex
  • Either a Mac with iPhone Mirroring, an Android phone with adb and developer options on, or a Phone Harness Cloud account
  • Your own hands to pair the phone, grant Accessibility and Screen Recording, or approve adb

Steps

  1. Install Phone Harness with uv using Python 3.12, for example uv tool install phone-harness. (inferred, check the README)
  2. Run phone-harness skill to register the skill with your coding agent.
  3. Run phone-harness doctor to check the connection to the phone.
  4. Start your test in the agent, asking it to use screenshot(), find_text, and tap on the target app.
  5. Read the agent's log and screenshots, then rerun with phone-harness cloud stop after a cloud session ends.

Prompt for your agent

Using the phone-harness repo at https://github.com/ShawnPana/phone-harness, open <app name> on the connected phone, follow the test script <script path>, and report each step with the screen text it read. Verify that the last screen matches the expected result in the script before reporting success.

Caveat. OCR sees text, not icons, so unlabeled buttons need a screenshot and a vision-capable model.

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