An iPhone app controls the same iPhone through a VPN that loops back into itself
A sideloaded app brings developer-device control back onto the phone, with VPN and privacy tradeoffs.
An iPhone controlling itself sounds like a shortcut until you follow the connection. This project routes through a loopback VPN to reach developer services on the very phone running the app. The device has effectively called its own technical support line and started pressing buttons.
The repository describes screenshot-and-action cycles. The app takes a screenshot, sends it to a vision model, receives a requested touch or other operation, then repeats. A Live Activity supplies a Stop button, and the run is saved as a chat. The model’s view is therefore a sequence of images and actions rather than an unrestricted understanding of every application.
A Mac is needed for the initial USB pairing file and for some build arrangements, but the project says it is unnecessary during a normal run. There is no additional control board and no jailbreak. That is the specific simplification: the runtime connection stays on the phone instead of depending on a nearby desktop to drive it.
The network boundary still deserves a careful read. Local control does not make the entire process local. Screenshots go to the configured model endpoint, so whatever appears in them may leave the device. A page containing private information remains private information when it has been captured as an image (pixels are surprisingly indiscreet).
The VPN has a practical cost as well. The README says iOS permits one VPN at a time, so another VPN, including a remote-network tool such as Tailscale, stops while this connection is active. On cellular, the project uses a shortcut to toggle data around establishing the loopback connection. That is a compatibility workaround a prospective user needs to know before relying on the app away from Wi-Fi.
Setup requires iOS 26 or later, Developer Mode, pairing and sideloading. Free-account and paid-development-team builds have different VPN arrangements; the free-account route also needs recurring signing. This is not an App Store installation with a single permission dialog. The project documents the extra setup instead of making no-Mac runtime sound like no preparation.
The example shown by the maker selects a ride and stops before booking. That stopping point matters: navigating toward an action and committing it are separate decisions. For initial evaluation, a harmless task with a clear expected result is easier to inspect than a workflow that can spend money or send a message.
The useful technical idea is the control route itself, together with the constraints it exposes. Removing the desktop from the live loop leaves the reader with fewer devices, while the permissions and the screenshot destination remain decisions that need an owner.
The phone is taking its own calls.