DIYgod's Pinky Puts Humans in Charge of AI Agents Controlling Phones
Pinky is an open-source MCP gateway that lets Claude Code, Codex and Cursor drive a real iPhone or Android phone with human approval gates baked in.
- Pinky lets AI agents drive real iPhone and Android phones over MCP from macOS, Windows or Linux.
- Approvals are enforced by a gateway process, not by instructions to the agent, blocking prompt-injection bypasses.
- Banking, wallet and password apps are hidden from agents by default; agents cannot type into password or OTP fields.
- On Android 13+, agents work on a hidden second screen so the phone stays locked and dark.
- Native Go app using MyGo on GPU: 14-18 MB download, ~70 MB RAM idle, Apache-2.0 licensed.
- Pre-alpha; works with Claude Code, Codex, Cursor, Claude Desktop and more via auto-configured MCP.
Pinky is a new Apache-2.0 desktop app that lets MCP-capable agents tap, swipe, and type on a connected iPhone or Android device. It runs on macOS, Windows, and Linux, mirrors the phone on the desktop, and lets the operator approve sensitive actions or take control. The repository has 5 stars.
DIYgod, the creator of RSSHub, built Pinky around the Model Context Protocol, an open protocol through which agents call external tools. A local gateway mediates phone access and records each run, giving developers a policy layer that remains separate from the model and its prompt. Pinky requires no account, although any data a connected agent sends to a remote model remains subject to that agent provider’s configuration and policies.
The gateway owns the veto
Each phone action passes through Pinky’s gateway, where approval rules are enforced independently of the agent’s instructions. On-screen text can still influence a model, but it cannot instruct the model to waive a gateway approval. This design reduces one common prompt-injection risk without eliminating detector errors or other failures.
- Default approval gates: payments, trades, and transfers wait for a human click.
- Optional approval gates: messages, orders, deletions, calls, installs, external links, and settings changes can require confirmation.
- Maximum review: operators can require approval for every step.
Pinky detects relevant buttons in 10 languages, according to the project documentation. Because that detection determines when an approval appears, developers should test the languages, applications, and interface variants used in their workflows.
This story is for Pro members
You've reached the end of the free preview. Upgrade to AlphaSignal Pro to read the full article - and everything else behind the paywall.