What the source did
- Almost nothing on his phone has an API. phonedriver gives Claude Code the phone: it reads the screen, taps, types and swipes in any app, on Android or iPhone.
- Bug hunt: he hid two bugs in a sign-up form and told Claude to "test the sign-up flow the way a careful tester would". It found both in 49 seconds and wrote numbered repro steps. In the nine benchmark runs before that, it found both planted bugs every time, and once it also reported two bugs he hadn't planted.
- Pizza run: on the real dominos.co.uk site, Claude (Opus 5.5) found the store nearest Leicester Square, put a large pepperoni in the basket, filled in guest checkout, and reached "Buy with GPay" in six and a half minutes.
- phonedriver held that tap and asked him. He said no.
- Claude never gets a screenshot. It gets the screen as a short numbered list, taps by number, and after each tap gets only the lines that changed. A screen read takes 13 ms, against 2.2 s for adb shell uiautomator dump.
- Benchmark, the project's own: on nine phone jobs with Sonnet 5.5, phonedriver passed 27 of 27 runs on 658k tokens. mobile-mcp passed 17 of 18 on 4.57M.
- Lesson he shares: tool descriptions are the most expensive text, since they're re-read every turn. He hid unused arguments, and the tool list went from 10,987 to 5,107 characters with nothing broken.
- Claude found a bug in the demo itself: a Pay tap inside a batch was held, but the question never reached him.
- Free, open source, no account and no telemetry, per the README. Install line: claude mcp add phonedriver -- npx -y phonedriver mcp.
- It doesn't make phone calls, because there's no audio.
- He calls it a side project for fun, and says that following an app's terms is on whoever uses it.
“I gave Claude Code a phone.”— u/Puzzled-Stick9170 (r/ClaudeCode), Reddit
Summary written by Agent Cookbook from the original post. See the original for the full context. How we source recipes
Our notes
- What it takes
- Claude Code or another MCP client, and the install line claude mcp add phonedriver -- npx -y phonedriver mcp. Android needs adb with wireless debugging, paired with phonedriver pair. iPhone needs a Mac with Xcode and your own developer certificate for the small test runner.
- Where it breaks
- The payment guard misses icon-only buttons and labels in languages it doesn't read. It can be switched off with autonomous: true or PHONEDRIVER_GUARD=off, which we don't recommend. It doesn't make phone calls, because there's no audio. Following an app's terms is on whoever uses it.
- Human checkpoint
- Keep the payment guard on, and add PHONEDRIVER_ASK=send,delete. You answer each held tap in Claude Code's own prompt, and the model never sees that question.
- Tools involved
- Claude Code, Codex, Cursor or any MCP client. The install command uses npx, Android: adb, with wireless debugging on. phonedriver pair shows a QR code to connect, iPhone: a Mac with Xcode, and your own developer certificate for the small test runner (phonedriver ios setup), Optional: phonedriver untether, for TCP mode, e.g. over Tailscale, You, approving every held Pay, Place order, Send and Delete tap
✓ Verified Source link checked and still live. Notes by Thomas, editor. How we verify
Get their template
Made and published by u/Puzzled-Stick9170. Start here; it is their original, not ours.
Their prompt
From u/Puzzled-Stick9170 Their exact wording for a bug hunt on a sign-up form. Source ↗
Approval rule
Set it up
- Install it with claude mcp add phonedriver -- npx -y phonedriver mcp. Or install the Claude Code plugin, which adds the skill as well. Use one or the other, not both.
- Android: there's no app to install. Turn on wireless debugging, then run phonedriver pair and scan the QR code. For TCP mode, for example over Tailscale, run phonedriver untether.
- iPhone: plug the phone into a Mac with Xcode, run phonedriver ios setup (a small test runner, signed with your own developer certificate), then switch to wifi mode.
- Set PHONEDRIVER_ASK=send,delete, so taps on Send, Reply, Post, Share, Delete and Remove are held as well as the default payment taps.
- Give Claude a plain goal. For a bug hunt, ask for numbered repro steps for each bug, as in the poster's prompt.
- When a tap is held, Claude Code asks you in its own prompt. Choose Allow, Allow for this session, or Decline. The poster declined the pizza order.
Common failures
- Turning the guard off. autonomous: true or PHONEDRIVER_GUARD=off removes the check. Keep it on.
- Trusting the guard on every pay button. It doesn't catch a payment button that is only an icon, or one labeled in a language it doesn't read.
- Expecting it to phone anyone. It doesn't make phone calls, because there's no audio.
- A target that moves. Each tap re-reads the screen just before it fires. If the target is gone, the tap fails and reports the closest match.
- Ignoring an app's terms. Following them is on whoever uses it, and an ordering site is a real service.
Variations
- It also works with Codex, Cursor or any MCP client, per the README.
- The Claude Code plugin adds a skill that tells the agent to send tap paths in one call. Don't install the plugin and the mcp add line together.
Related setups: Claude Code phones a restaurant with Smitline → · $15 phone line: your agent calls from your real number → · Slack Approve/Cancel gate for Claude Code bots → · Get notified when your coding agent needs you →
Get the 10 best agent setups. Free.
Plus new recipes every week. One email, no spam.
Unsubscribe anytime. Privacy