DIYgod dropped Pinky on GitHub on November 6, 2026, and it hit version 2026.1115.4 on November 15 at 02:38 UTC. This Apache 2.0 desktop bridge acts as a Model Context Protocol server, letting agents like Claude Code or Cursor operate a real iPhone or Android device. The codebase already shows 2,158 stars, 235 forks, and 1,352 commits, signaling rapid adoption in the agent community.
The Agent Surface and Tooling
Pinky exposes 26 tools via JSON-RPC 2.0 over standard input, all prefixed with 'phone_' (e.g., phone_connect, phone_tap). It supports major agents including Codex, VS Code, and Gemini CLI. The tool ships no model of its own; users pick the brain, whether it's DeepSeek, GPT, or a local Ollama instance. The ~35 MB binary runs on Linux, macOS, or Windows without needing an account, API key, or GPU.
Gateway-Based Safety Controls
The core innovation is moving approvals out of the prompt and into the gateway. An agent cannot approve its own actions, even if screen text tries to trick it. By default, payments, trades, and transfers require a human click. The gateway also hides banking and password-manager apps from the agent, preventing it from typing into sensitive fields unless explicitly allowed for a single task.
Audit Trails and Device Compatibility
A Tokenstrom code review confirmed that only the desktop interface can grant approvals, with requests timing out after 60 seconds. Each approval is tied to the specific session, device, and arguments. On Android 13+, agents work on a hidden second screen, while older devices use the main screen. Every action is recorded with screenshots and screen recordings, exportable as HTML reports that stay on the user's computer.
Key Takeaways
- Pinky is pre-alpha and designed for single-device use with a human in the loop, not unattended device farms.
- The approval model is the authors' claim and not yet independently tested, with button detection cited as a potential weak link.
- The project releases updates every few hours, reflecting its nine-day-old status and rapid development cycle.
The Bottom Line
Pinky proves that agent safety belongs in the gateway, not the prompt. Its human-gated architecture offers a compelling pattern for controlling AI actions on physical devices.