Cursor launches an iOS app to control AI coding agents remotely

Cursor for iOS is really two products stacked in one icon. The first is a cloud-agent launcher: you pick a repository, choose a model, and fire off an agent that runs in an isolated virtual machine with a full development environment to test, verify, and demo its work, then comes back to you with a merge-ready pull request ^[1]. This is asynchronous by design - you kick off work "when ideas strike," get a notification when it's ready, and merge on the go ^[1].

The second product is the headline feature and the harder one: Remote Control, which lets you keep steering an agent already running on your local Mac or PC, provided that host machine stays awake (the app ships a keep-awake setting for exactly this) ^[1]. The app is built around handoffs between these two worlds - send a local plan up to a cloud agent, move an active agent to the cloud, then pull the session back down to your computer to test before merging ^[1]. That seam between local and cloud is where the ambition lives, and as the community reaction below shows, it's also where the launch is rough.

A coding app with no editor sounds absurd until you accept the premise underneath it: the developer's job is changing from writing code to managing agents that write it. Industry observers cited by Tekedia and The Next Web make the argument plainly - once agents handle the actual typing, the human role collapses to supervision and decision-making, tasks that do not need a full IDE or a powerful desktop ^[3]. Commentators have started calling this "ambient software engineering," where agents grind continuously in the background and the developer periodically checks in on progress ^[4].

The most striking endorsement comes from a competitor. Boris Cherny, who heads Claude Code at Anthropic, says most of his coding now happens on his phone and that he'd have called that crazy six months ago ^[2]. When the person running a rival coding agent volunteers that the phone has eaten his desktop workflow, the trend is not a Cursor marketing line - it's an industry shift Cursor is racing to package. Cursor leans into the same psychology with a name for the anxiety it's selling against: "FOMAT," or Fear of Missing Agent Time, the idea that you shouldn't lose agent productivity just because you stepped away from a desk ^[1].

Here is the tension at the heart of this release: the single feature users want most - remotely controlling the agents already running on their own machine - is the one most widely reported broken at launch. On r/cursor, the official announcement post drew an active thread in which multiple developers reported that enabling remote control or typing the /remote-control command still surfaced only cloud agents, that the remote-control option was missing from settings entirely, and that "the local proxy isn't working." A separate bug report described the app correctly seeing repositories and branches but erroring out the moment a prompt was sent. A Cursor moderator was troubleshooting live, telling users to verify their GitHub connection at cursor.com/agents and to confirm that git remote -v returns a valid remote.

The cloud path, notably, drew far fewer complaints - the friction is concentrated exactly on the local-control promise that the marketing leads with. On X, sentiment ran strongly positive and excited, with the official launch announcement framing the app as "more than a companion app" and the community amplifying a "ship from your couch" mobility narrative around remote agent control and the Composer 2.5 discount. The gap between that enthusiasm and the Reddit bug reports is the real launch-day story: the idea has captured imaginations faster than the v1 implementation can deliver on it.

The iOS app is also a distribution play for Cursor's own model. Running inside the app is a 75%-off promotion on Composer 2.5 through July 5, 2026, an incentive that pushes mobile adoption and steers users toward Cursor's in-house model rather than the OpenAI, Anthropic, or Google frontier models the app also supports ^[1]. The competitive logic is straightforward: Anthropic and OpenAI already offer mobile interactions for their coding tools, so shipping a deep, agent-native iOS app helps Cursor differentiate and keep developers inside its ecosystem ^[3].

The most-requested missing piece tells you who Cursor is betting on first. The loudest theme across community discussion was demand for an Android version; a moderator said Android is "being worked on" but gated on team size, with the framing that "good software requires work and ownership." That prompted a vocal "Apple favoritism" backlash from developers who note that iOS-first is out of step with the Android and Windows majority, countered by defenders who argued those platforms are simply harder to build for. Either way, Cursor chose to plant its flag on the surface where it could ship the deepest agent experience fastest, and to subsidize its own model on the way in - a platform bet, not just a feature release.