Test an app signup flow by letting Claude Code tap through a phone

A Redditor gave Claude Code control of a real phone through their phonedriver MCP tool, and it found two planted bugs in a signup form in 49 seconds, then took a Domino's order to the payment screen.

Done withClaude Code· Nov 13, 2026

What they did

u/Puzzled-Stick9170 built phonedriver, an open-source MCP server that lets Claude Code read the screen of an Android or iPhone and tap, type and swipe in any app. Instead of screenshots, the agent gets the screen as a short numbered list, taps by number, and after each action receives only the lines that changed. To test it, the poster planted two bugs in a signup form: the welcome message cut off the last character of the email, and the Create button ignored the next tap after one rejected submit. Claude Code was told to test the signup flow like a careful tester. In a second run, Claude (Opus 5.5) was asked to order a large pepperoni on the real Domino's UK site from the store nearest Leicester Square.

How it went

Claude found both planted bugs in 49 seconds and wrote numbered reproduction steps for each. The poster says it found both in all nine earlier benchmark runs, and once reported two bugs they had not planted. The pizza run reached the Google Pay button in six and a half minutes, filling in guest checkout on the way; the poster declined the payment. On nine phone jobs with Sonnet 5.5 the tool passed 27 of 27 runs on 658k tokens, against 17 of 18 on 4.57M tokens for mobile-mcp, by the author's own count.

Worth knowing

The benchmarks are the author's own, for their own tool. phonedriver holds any tap on Pay or Place order and asks first, but while recording the demo a Pay tap sent inside a batch of actions was held without the question ever reaching the poster, a bug Claude Code caught. The phone has to be in developer or debug mode. A commenter asked whether popups that appear between a screen read and a tap are caught; that went unanswered.

Try it

With Claude Code· 4 parts to fill in

You can control my phone through [phonedriver or my phone-control MCP tool]. Open [app name] and test the [signup or other flow] the way a careful QA tester would: try valid input, bad input, retries after errors and edge cases like [long emails or special characters]. For every bug you find, write numbered steps to reproduce it, what you expected and what happened. Never tap anything that pays, places an order or sends a message without asking me first. Stop when you have covered the flow and give me the list.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related