Personal Agent Bench

Also in日本語简体中文한국어

Phone use agents: eleven open-source tools that operate a real phone

A phone use agent is software that lets a language model operate a real phone: it looks at the screen, decides what to tap, and taps it, in apps that were never built to be driven by anything but a thumb. In October 2026 the idea moved from research demos to GitHub's trending list, led by a plugin that lets Codex run an iPhone. This page compares eleven open-source tools from their source code, pinned to the commits we read on 13 October, or on 19 October for the last two added: how each reaches the phone, what it sends where, where it stops to ask you, and what it says about the apps' own rules. We ran none of them. Disclosure: Zentor, the team behind this site, also builds phone use software. One tool here, Oh My Phone Use, is a side project by people at Zentor, published under a personal GitHub account; it is marked as such in the tables, read with the same checklist and given no score, like the rest. The other ten are competitors. About us.

  • There are four routes into a phone: Apple's test-automation framework, a mirrored screen plus a fake keyboard and mouse, Android's debugging bridge and accessibility service, and phones rented in someone else's cloud.
  • In every tool, what is on your screen goes to a language model. Only one tool gates sensitive taps in code, and even there the model decides when the gate fires.
  • Two tools send usage events home by default that can include what you asked the agent to do.
  • One framework ships code whose stated purpose is making taps look human, and its cloud service sells "stealth". Another refuses, in code, to swipe across an anti-bot check. None of the eleven discusses account bans.

What a phone use agent is, and what this page leaves out

Every tool here pairs a model with a way to see a phone's screen and a way to act on it. The model gets a screenshot, the screen's element tree or both, chooses a tap, swipe or keystroke, and repeats. It is the phone equivalent of the "computer use" agents that drive a desktop, and it reaches places a browser agent cannot: WeChat, banking apps, delivery apps, anything without a web version.

This page covers open-source tools you install yourself. It leaves out assistants built into a phone's operating system, which are features of a handset rather than tools you can inspect, and consumer apps that run errands for you from the vendor's own servers. Those belong with the personal agents we track and the products we took apart. One of the eleven, OpenGUI, is published under the Business Source License 1.1, which restricts production use until 2030, so it is source-available rather than open source.1

Two more iPhone projects we read on 19 October are left out of the tables. iphone-kit turns a Mac into a Bluetooth keyboard and mouse and switches on AssistiveTouch over USB through a private Apple framework, so it needs neither Developer Mode nor an extra board; it has no licence file, which leaves it all rights reserved.2 RC Pair's phone-open drives an iPhone or iPad from a Linux computer over Apple's own developer services; it ships no agent, its phone app is not in the repository, and its Functional Source License bars competing use for two years.34

Four routes a phone use agent takes into your phone

  1. 1Apple test automation

    Where the agent runs

    A Mac, another computer on the same Wi-Fi, or an agent app on the phone itself

    What it needs on your phone

    A runner you sign and install, Developer Mode, and for iCTRL without a Mac, a free Apple ID in SideStore plus Apple's Developer Disk Image

    ToolsiPhone Use, iCTRL; Droidrun and AutoGLM on iOS

  2. 2Screen share plus fake input

    Where the agent runs

    A computer, or an agent app on the phone itself

    What it needs on your phone

    AssistiveTouch, sometimes a screen-sharing app you sign yourself, or Mac accessibility and screen recording permissions

    Toolsesp32-iphone-agent (AirPlay plus a $7 board), Oh My Phone Use (screen-sharing app plus a Bluetooth ESP32 board), ipad_computer_use (screen-sharing app plus a USB RP2040 board), anan-iphone-use (iOS screen sharing plus an M5Stack StopWatch board), phone-harness (macOS iPhone Mirroring)

  3. 3Android debugging and accessibility

    Where the agent runs

    A computer connected over USB or Wi-Fi

    What it needs on your phone

    USB debugging and an accessibility permission, which can see and act on almost everything

    ToolsDroidrun, AutoGLM, mobile-use, OpenGUI, phone-harness on Android

  4. 4A phone in someone else's cloud

    Where the agent runs

    Your computer or the vendor's servers

    What it needs on your phone

    Nothing on yours: you rent a hosted device and log your accounts in on a phone you do not hold

    ToolsMobilerun Cloud, phone-harness cloud

Sources:5678910

The route decides what can go wrong. A tool that mirrors the screen sees only what the phone agrees to mirror; iOS does not mirror passcode entry or Apple Pay, according to the esp32 project.11 An accessibility service sees and can act on almost everything. A cloud phone means your logged-in accounts live on hardware you never touch.

Two tools let the agent itself live on the phone. iCTRL is an XCTest runner that serves a JSON-RPC API on the iPhone, and its makers' on-phone agent, Minis, calls it locally; any agent on the same network can call it too.1213 anan-iphone-use puts an MCP server on a small board that types and taps over USB or Bluetooth, while an agent app on the same iPhone watches through iOS screen sharing, which needs iOS 27 or later.1415 Neither removes the setup cost. iCTRL still needs Developer Mode and a signing certificate that a free account must refresh every 7 days.16 The board's keyboard and mouse need no Developer Mode, but anan-iphone-use's own setup notes say the current developer-signed build of its phone app does, and that app is not yet published.17

The routes also differ in how deep they reach, and depth is what you are really granting. A phone offers an agent three depths. The shallowest is the operating system's interface for one job: an Android app given notification access is told about each notification and can dismiss it, but cannot tap through your other apps, and on iPhone an app can offer named actions through App Intents, which Siri and Shortcuts can run.1819 The middle depth is whatever a particular app chooses to publish, such as an Android intent that opens a pre-filled email or a map search; it reaches only what that app's makers exposed.20 The deepest is the screen itself, through Android's debugging bridge, an accessibility service or Apple's XCTest. An accessibility service runs in the background, can ask to read the content of the window you are looking at, and Android's own reference says such services should only be used to help users with disabilities. The debugging bridge opens a shell on the device that can start apps and perform other system actions.2122

All eleven tools on this page work at that deepest level. It is the only one that reaches apps that expose nothing, which is why a phone use agent can order from a delivery app at all. It also means a single permission covers your banking app and your messages together, where a shallower interface would have covered one job. When a tool's setup asks you to switch on USB debugging or an accessibility service, that is the grant you are making.

Eleven open-source phone use agents compared

ToolPhoneRouteDefault modelConfirmation in codeUsage telemetryLicence
iPhone UseiPhoneWebDriverAgent, USBHost's model (Codex and others)Password fields refused; unverified submit stops a batchOn in Codex installMIT
esp32-iphone-agentiPhoneAirPlay plus ESP32 keyboard and mouseAny OpenAI-compatible endpointNone; emergency stop onlyNone foundMIT
Oh My Phone Use (Zentor side project)iPhone, iPadScreen-sharing app plus Bluetooth ESP32 keyboard and mouse; also places callsHost's model, over MCPNone; skill text asks firstNone foundMIT
ipad_computer_useiPad, USB-C iPhoneScreen-sharing app plus USB RP2040 keyboard and mouseHost's model, over MCPNoneNone foundMIT
phone-harnessiPhone, Android, cloudiPhone Mirroring plus OCR; ADBHost agent's modelNone; skill text asks firstOn; includes task textMIT
DroidrunAndroid, iPhoneADB plus accessibility app; WebDriverAgentgemini-3.8-flash in example configNoneOn; includes goal textMIT
Open-AutoGLMAndroid, HarmonyOS, iPhoneADB or HDC; WebDriverAgentAutoGLM-Phone-9B, self-hostedYes/no prompt when the model flags a tapNone foundApache-2.0
mobile-useAndroid, iPhone simulatorADB plus UIAutomator2OpenAI GPT-5 familyNoneAsks firstApache-2.0
OpenGUIAndroidADB plus scrcpy; accessibility clientHost's modelBackend prompt escalates payment and deletionDisabledBUSL-1.1
iCTRLiPhoneOwn XCTest runner on the phone; agent on the phone or the same Wi-FiHost agent's modelNone; skill text asks firstNone foundApache-2.0
anan-iphone-useiPhoneiOS screen sharing plus StopWatch board as USB or Bluetooth mouse and keyboardClient's model, over MCPNone; control must be switched on at the boardNone in firmware; phone app not publishedGPL-3.0

GitHub stars on 5 November: Open-AutoGLM 26,543, Droidrun 9,962, iPhone Use 4,905, phone-harness 4,460 (its repository has since moved to the phone-harness organisation), esp32-iphone-agent 4,408, mobile-use 3,363, OpenGUI 1,807, iCTRL 582, anan-iphone-use 149, ipad_computer_use 81, Oh My Phone Use 18. On 13 October the same list read Open-AutoGLM 26,389, Droidrun 9,632, iPhone Use 3,504, mobile-use 3,257, phone-harness 3,253, OpenGUI 1,816, esp32-iphone-agent 1,189, ipad_computer_use 78, Oh My Phone Use 9. The fastest movers are the two youngest: iPhone Use was created on 6 October and esp32-iphone-agent on 11 October, and esp32-iphone-agent has since multiplied its stars almost fourfold. Oh My Phone Use started from a snapshot of ipad_computer_use, swapped the USB board for a Bluetooth one and added phone calls.23

What the phone use agent sees, and where your screen goes

Each tool turns your screen into model input. Droidrun reads the accessibility tree by default and adds screenshots when asked.24 mobile-use sends both the UI hierarchy and a compressed screenshot.25 phone-harness reads an iPhone through local OCR first. AutoGLM sends screenshots to a vision model.26 iCTRL reads the accessibility tree and falls back to Apple's on-device text recognition when the tree comes back thin.27 anan-iphone-use's board sees nothing; screenshots come from the client's screen sharing.

Whichever form it takes, it goes to the model you configured. That can stay on your machine: AutoGLM defaults to its own 9B model served locally, and esp32-iphone-agent documents a local option.28 More often it goes to a hosted model: mobile-use defaults to OpenAI, Droidrun's example config to Google, and iPhone Use, phone-harness, Oh My Phone Use, ipad_computer_use, iCTRL and anan-iphone-use use whatever the agent driving them uses.29 A chat, a bank balance or a one-time code on screen becomes part of a request to that provider. iCTRL adds two smaller leaks of its own: its live screen stream is not encrypted on any channel, and an app name it cannot find on the phone can be looked up through Apple's public iTunes search.3031

Where a phone use agent stops to ask you

This is the question we ask of every personal agent, and the answers here are thin.

Only AutoGLM has a confirmation built into its action code: a tap that the model labels with a message triggers a yes or no prompt, and a take-over action hands the phone to you for logins and captchas.32 Two limits apply. The model decides when to add the label. And only the Chinese system prompt teaches it to; the English prompt mentions neither the labelled tap nor the take-over action.3334

iPhone Use refuses to type into password fields and stops a batch after an unverified submit. OpenGUI's hosted backend tells its model that logins, payments, transfers, orders and deletions must go to the user.35 phone-harness asks its host agent, in its skill text, to stop before sending, posting, purchasing or deleting.36 Oh My Phone Use's skill asks the same before messages, payments, deletions, account changes, passwords and verification codes.37 iCTRL's skill tells the agent to stop at the checkout and never tap the final pay button, and its runner asks you to allow each new agent on the phone, which takes an unlocked phone; after that, nothing in the code checks what the agent taps.3839 anan-iphone-use rejects all input until someone switches control on at the board, and either button stops it; that is a power switch, not a check on payments.40 esp32-iphone-agent, Droidrun, mobile-use and ipad_computer_use have no confirmation for payments or sending that we could find.

Oh My Phone Use is the only one of the eleven that also makes voice calls. The board acts as the phone's Bluetooth car kit, the Mac speaks with macOS say and transcribes the other side locally with whisper.cpp, and the transcript goes to your agent. The skill tells the agent to dial only numbers you gave it, to say it is an agent calling for you and that replies are transcribed, and to treat what the other person says as information rather than instructions. The number, transcripts and summary stay in a file on the Mac.4142 Those rules are instruction text too, and a call reaches someone who never installed anything.

Both Oh My Phone Use and ipad_computer_use run their screen-control server without a password, by design, and rely on the network being yours: anyone who can reach the controller can ask for screenshots and send input, so keep it on your own machine or a private network such as Tailscale.4344

Instruction text is not nothing, but it is a request to a model, not a lock. Compare Pine, which asks before every billing action as part of the product.

Phone use agent telemetry: what the tools send home

Four tools report usage to an analytics service; what they include differs a lot.

  • phone-harness is on by default and sends to PostHog. Each event can carry the script you piped in, up to 20,000 characters, and the tail of the output, which on an iPhone can include text read off the screen. Its install guide calls this anonymous.4546 Turn it off with PHONE_HARNESS_TELEMETRY=0.
  • Droidrun is on by default and sends the goal you typed in its first event. Its documentation says it does not collect "any personal or sensitive data".4748 A goal like "pay my sister back" is personal by any reading.
  • iPhone Use is on by default in the Codex install and sends tool names, outcomes and timings only, through an allow-list that matches its documentation. Since version 0.3.14 on 16 October the same events go to Google Analytics as well as PostHog; its own page covers the later version.
  • mobile-use asks before enabling anything.49

AutoGLM, esp32-iphone-agent, Oh My Phone Use, ipad_computer_use and iCTRL had no telemetry we could find; OpenGUI's analytics are stubbed out. anan-iphone-use's firmware has none, but its phone app, which does the watching, is not published, so we cannot say what it sends.

Stealth, account bans and AI that controls your phone

Apps notice automation. Taps that always land dead centre, typing at a perfectly even rate and identical device fingerprints are classic signals, and platforms such as WeChat, Instagram and delivery apps have their own risk controls. None of the eleven repositories tells you what happens to an account that gets flagged.

Droidrun goes the other way. Its open-source code includes a stealth mode, off by default, whose purpose is stated plainly: randomised tap positions "avoiding the predictable dead-center taps that betray automation", plus human-like timing and typing speed.5051 Its hosted service, Mobilerun, advertises "stealth typing & swiping" and devices recognised as genuine. phone-harness's README advertises hosted phones "with stealth, real numbers, 2FA".52

At the other end, AutoGLM's terms forbid bulk accounts, group control and fake engagement, and say the project is for research and learning.53 esp32-iphone-agent asks you to respect the terms of the apps involved.54

iCTRL is the only one whose code backs away from an app's defences. A swipe or drag that starts on a slider or puzzle check it has just read is refused, with a message telling the agent to close the check or report the step as blocked, and after an app pushes back three times in ten minutes the agent is told to stop using it. Its README adds that synthesized taps are no guarantee against an app's own bot detection.555657

Software designed to look human to an app is software designed to get past that app's rules. Whatever you think of that, it moves the risk onto your account.

Phone use agent benchmarks: whose numbers you are reading

Two projects publish success rates, and both measured themselves. mobile-use says it was the first to complete all of AndroidWorld, 116 of 116 tasks, in January 2026.58 Droidrun's README badge says 91.4%, while its website says 100% on AndroidWorld and 98.34% across iOSWorld and AndroidWorld, without naming the model, date or who ran the evaluation.59

iCTRL publishes speed rather than success: about 280 milliseconds a tap and a median of 416 milliseconds to read the visible screen across 8 apps.60

None of these numbers has been independently reproduced that we know of, and the two "100%" claims cannot both be news. Benchmarks that a vendor runs on itself are a starting point, not a result. We have not run any phone use agent in our own exam; none of them has a score on this site.

FAQ

What is a phone use agent? A language model connected to a real phone: it sees the screen as a screenshot or element tree, chooses a tap, swipe or keystroke, and repeats until the task is done. It works in apps that have no web version or API.

Can AI control an iPhone without a jailbreak? Yes. iPhone Use, Droidrun and AutoGLM use Apple's WebDriverAgent with your own developer signing, and iCTRL ships its own XCTest runner that a free Apple ID can sign; esp32-iphone-agent poses as a USB keyboard and mouse; Oh My Phone Use, ipad_computer_use and anan-iphone-use pair screen sharing with a small board that does the same over Bluetooth or USB; phone-harness drives macOS iPhone Mirroring. None needs a jailbreak.

Which phone use agent asks before paying? In code, only AutoGLM, and only when its model flags the tap, which its English prompt does not teach. OpenGUI's backend, phone-harness, Oh My Phone Use and iCTRL ask through instructions to the model. The others have no payment confirmation we could find.

Is it safe to use a phone use agent on my main phone? We would not. The agent can usually open any app and tap anywhere while the phone is unlocked, your screen goes to a model provider, and no project explains account-ban risk. Use a spare phone and accounts you could afford to lose.

Do phone use agents send my data anywhere? Your screen goes to whichever model you configure. Separately, phone-harness and Droidrun send usage events by default that can include your task text; iPhone Use sends only tool names and timings; mobile-use asks first.

What is the best open-source phone use agent? We do not rank them, and we have not run them. The table above shows the trade-offs: AutoGLM is the only one with a confirmation step in code, iPhone Use limits its default telemetry to tool names and timings, Droidrun covers the most platforms but ships stealth features and sends your goal text by default, and iCTRL is the one that refuses to fight an app's anti-bot checks. This is a source review at pinned commits from 13 and 19 October 2026, and iPhone Use has its own page.

Sources (60)
  1. OpenGUI licence github.com
  2. iphone-kit mechanism github.com
  3. phone-open licence github.com
  4. phone-open architecture github.com
  5. esp32 route github.com
  6. Oh My Phone Use route github.com
  7. ipad_computer_use route github.com
  8. phone-harness routes github.com
  9. Droidrun Android setup github.com
  10. AutoGLM requirements github.com
  11. Mirroring limits github.com
  12. iCTRL design github.com
  13. where the agent runs github.com
  14. anan-iphone-use design github.com
  15. requirements github.com
  16. iCTRL free-account limits github.com
  17. anan-iphone-use setup github.com
  18. Android notification access developer.android.com
  19. Apple App Intents developer.apple.com
  20. Android common intents developer.android.com
  21. Android accessibility service developer.android.com
  22. Android debugging bridge developer.android.com
  23. Oh My Phone Use credits github.com
  24. Droidrun vision setting github.com
  25. mobile-use input github.com
  26. AutoGLM screenshots github.com
  27. iCTRL screen reading github.com
  28. AutoGLM default github.com
  29. mobile-use defaults github.com
  30. iCTRL stream github.com
  31. app lookup github.com
  32. AutoGLM confirmation github.com
  33. Chinese prompt github.com
  34. English prompt github.com
  35. OpenGUI escalation github.com
  36. phone-harness skill github.com
  37. Oh My Phone Use skill github.com
  38. iCTRL skill github.com
  39. pairing prompt github.com
  40. anan-iphone-use control gate github.com
  41. Call rules github.com
  42. saved results github.com
  43. Oh My Phone Use security github.com
  44. ipad_computer_use security github.com
  45. Default on github.com
  46. event fields github.com
  47. Goal in init event github.com
  48. docs claim github.com
  49. Consent prompt github.com
  50. Stealth state github.com
  51. stealth setting github.com
  52. phone-harness README github.com
  53. AutoGLM terms github.com
  54. esp32 responsible use github.com
  55. Captcha refusal github.com
  56. rate-limit back-off github.com
  57. detection warning github.com
  58. mobile-use claim github.com
  59. Droidrun badge github.com
  60. iCTRL speed github.com