Pinky lets MCP agents drive phones with approval gates
DIYgod/pinky puts an approval layer between MCP agents and real phones, with iOS and Android support in a pre-alpha release.
A pre-alpha phone agent with a gatekeeper
On 2026-11-14, the DIYgod/pinky project described a pre-alpha tool for Pinky MCP phone automation: an MCP-capable agent can operate a real iPhone or Android phone while a person watches a mirror of the screen on a computer, approves risky steps and reviews what happened. The Pinky GitHub repository reported 2,104 stars and 228 forks, gathered in the eight days since the project was created on 2026-11-06. It is written in Go and released under Apache-2.0.
What the source confirms
Pinky has one desktop app for macOS 13 or later, Windows 10 or 11 64-bit x64, and 64-bit Linux with Ubuntu 20.04, Debian 11 or newer and GTK 3. It drives Android 10 to 17 and iPhones on iOS 17.4 or later. On iOS 27 and later nothing needs to be installed on the phone; on iOS 17.4 to 26, Pinky's iPhone app is installed once from a Mac with Xcode.
The app connects Claude Code, Claude Desktop, Codex, Cursor and other MCP-capable agents, on the same computer or over HTTP. Pinky can also do tasks itself with a chosen model, including DeepSeek, Qwen, Kimi, GLM, Claude, GPT, Gemini and local models in Ollama or LM Studio. The download is 16 to 22 MB, and the source says it idles at about 70 MB of memory and 0% CPU on a Mac. It is free, open source and needs no account.
How the approval layer works
The important design choice is that Pinky's gateway enforces approvals, not instructions to the agent. Payments, trades and transfers wait for a click by default. Settings › Safety can also make sends, orders, deletions, calls, installs, outbound links and settings changes wait, or require approval for every step. Pinky detects these buttons in 10 languages, and the source says an agent cannot approve itself even if on-screen text tries to persuade it.
Banking, wallet and password-manager apps are invisible to agents by default, and agents cannot type into password or one-time-code fields. If a task needs a banking or wallet app, the agent must ask, and the user can allow it for that task only. Every new agent needs approval and gets only the scope the user grants.
The source's example is a Claude Code run on an Android 16 emulator. Pinky asks before payments by default, and that run also asked before messages. On Android 13 and later, agents work on a hidden second screen while the user keeps the main screen. Older Android phones and iPhones use the main screen. The source also describes saving a phone PIN in Pinky so an agent can unlock a phone, with each unlock confirmed by Touch ID, Windows Hello or the keyring password. Agents never see the PIN.
Records, reach and limits
Each run is recorded in plain words, screenshots and a screen recording with a mark per step, exportable as an HTML report, and the source says the record stays on the computer. Scheduled tasks and memory work on the computer and on Android. The project is still pre-alpha. The source says Claude Code has used real phones end to end, including an Android phone over USB, an iPhone on iOS 27 and an iPhone XS Max on iOS 18.7.11 through Pinky Helper. Pinky on the phone has completed tasks with a real model on a Mi 10 Pro running Android 17 and an iPhone 13 mini on iOS 27.0.1. Some built features still wait for a person to try them.
What this likely means
For builders, the source suggests that phone automation needs permission design as much as model quality. A gateway outside the model is a pattern likely to matter wherever an agent can spend money, send messages or change settings. The source gives no independent security testing, battery impact, latency figures or complete support matrix. Because approval detection depends on recognising buttons, this likely works less predictably on custom interfaces, though the source says 10 languages are covered.
What it means for building apps with AI
Pinky is a phone-control tool, not a web app builder. Draftship is an AI app builder that writes, builds and hosts web apps from plain language, and its documentation on adding AI to your app covers the in-app side, not phone control or MCP. The source gives no indication that Draftship is connected to Pinky.
Primary sources
- DIYgod/pinky: Let AI use your iPhone or Android phone, with you in the loop: any MCP agent from macOS, Windows or Linux, or Pinky itself, right on the phone. · GitHub trending AI repositories, Nov 14, 2026
This article was drafted with AI assistance from the primary sources listed below and checked automatically against them. An editor hasn't reviewed it yet.