Pinky is available as a public, Apache-2.0-licensed pre-alpha gateway that lets MCP-capable agents operate supported Android phones and iPhones while the owner watches, approves risky actions or takes control. For developers, the immediate consequence is that agents including Claude Code, Claude Desktop, Codex and Cursor can reach mobile interfaces from macOS, Windows or Linux, with agent connections available over stdio or HTTP. The project describes the gateway, supported agents and desktop platforms in its repository.
Gateway-enforced approvals
Payments, trades and transfers require approval by default. Users can also require confirmation for sends, orders, deletions, calls, installations, links that leave an app, settings changes or every step. Pinky says these rules run in its gateway rather than in instructions given to the agent, preventing an agent from approving its own action; the project claims to identify relevant buttons in 10 languages. Pinky documents these approval categories and their enforcement model on its project page.
The gateway also hides banking, wallet and password-manager apps from agents by default, and it prevents agents from typing into password or one-time-code fields. A user can temporarily allow a banking or wallet app for a specific task, while each newly connected agent requires approval and receives only the scope the user grants. Those default restrictions and per-agent scopes are described in the repository.
Device coverage and run records
Pinky documents support for Android 10 through 17 and iOS 17.4 or later. Its desktop application runs on supported versions of macOS, Windows and Linux, while Android emulators and iOS Simulators can stand in for physical devices. The repository lists the operating-system, phone and simulator requirements.
On Android 13 and later, an agent can work on a hidden secondary display, leaving the phone’s primary screen available to its owner or switched off and locked. Older Android devices and iPhones use the main display. Clicking the desktop mirror pauses the agent for manual control, and touching an Android phone also pauses it. Pinky’s documentation explains its display behavior and takeover controls.
Each run can include plain-language step descriptions, screenshots and a screen recording marked by step. Pinky says these records can be exported as an HTML report and remain on the user’s computer. The project page documents its recording and export features.
Analysis: the boundary still needs testing
Analysis: Moving approval enforcement outside the agent’s instructions is Pinky’s most consequential design choice because it gives the agent no stated route to approve itself. The unresolved issue is recognition: where a rule depends on Pinky spotting a risky on-screen button, its practical protection depends on what the gateway correctly classifies. The repository claims coverage across 10 languages, but it also labels the software pre-alpha and says some built functionality still awaits testing by a person. That makes the gateway a security design to evaluate, not evidence that every mobile workflow will be classified correctly. Pinky states both its button-detection scope and its pre-alpha testing status in the repository.
The project reports end-to-end Claude Code runs on physical Android and iPhone hardware, alongside support for USB or Wi-Fi connections and computer-based unlocking. It directs prospective users to its acceptance documentation for the current feature status and testing instructions. Those implementation-status claims come from Pinky’s own project page.
