Give Your Agent a Real Phone

Some app work only happens on a phone. Walking through your own onboarding after a release. Checking what a competitor's paywall looks like this week. Posting the clip you made to Instagram. Your agent can plan all of that, but it has never had hands to do it.

Phones gives your agent a real phone: the iPhone or Android phone plugged into your Mac. Claude, Cursor, or Codex sees the screen, taps, types, and scrolls, one step at a time, through Appeeky MCP. Anything that would post, send, or pay waits for you first.

Real devices, real apps — no simulator, no recording
Works with the agents you already use over MCP
Post, Share, Send, Buy, and Delete taps stop and ask you, with a screenshot of what the agent was looking at
Your phone never leaves your Mac

Plug in, turn it on

Open Appeeky Desktop, turn on Settings → Phones, and plug in a phone.

Android: turn on USB debugging.
iPhone: turn on Developer Mode. The first time, Appeeky Desktop prepares the iPhone for automation on its own. It takes about a minute.

Your Mac shows up on the Phones page in the dashboard, with every phone it shares. From then on, any agent connected to Appeeky MCP can use them.

What the agent actually does

Give it a task in plain words: "Open Settings, go to Display, and turn on Dark theme." The agent looks at the screen, picks one action, does it, and looks again. It works from the elements on screen, not from guessed coordinates, so it copes with apps it has never seen.

It is careful in the places agents usually aren't. Before it taps a switch, it reads whether the switch is already on. It only says it's done when the newest screen shows the result, and its summary describes that screen, not what it hoped would happen.

Some things to try:

Your own release: open the new build, go through onboarding and the paywall, and screenshot every step
Competitors: install their app, read the paywall and the pricing, and note what changed since last month
Store pages: open your App Store or Google Play listing on a real device and check what users see first
Posting: share the video you made in Studio to Instagram or TikTok from the phone it belongs on

Nothing goes out without you

Taps that commit something to the outside world — Post, Share, Send, Publish, Buy, Pay, Subscribe, Delete — don't happen on their own. The agent stops, and the request shows up on the Phones page with a screenshot of exactly what it was about to tap. You get an email too.

Approve, and the agent carries on. Deny, or let it sit for ten minutes, and the agent stops and tells you why. An agent can't approve its own request: only you, signed in to Appeeky, can decide.

Your phone stays yours

The phone stays plugged into your Mac. Appeeky Desktop opens one outbound connection to Appeeky, signed in as you, so there are no ports to open and nothing to expose. Only agents acting for your account can see or use your phones, and sharing stops the moment you turn it off or close the app.

We don't record the screen. The only screenshots we keep are the ones attached to approval requests, so you can see what you approved.

Coming soon: your Co-founder

Next, your Co-founder agent gets the same hands. It already watches your metrics, reviews, and competitors every day. Soon it will open the phone when something changes: walk through a competitor's new onboarding the day it ships, screenshot the paywall that moved, or check your own release on a real device before you hear about a bug. The same approvals apply, so it still asks you before anything goes out.

Built on agentthumbs

Under the hood, Phones runs on agentthumbs, our open package for giving agents real phones. If you'd rather run it yourself, it works on its own from the command line and over MCP.

Phones is rolling out in beta. Update Appeeky Desktop, turn on Settings → Phones, and ask your agent to open something.