Cursor adds cloud handoff from mobile for agents that keep running

• Cursor now lets developers hand a local agent off to the cloud so it can keep running after the laptop closes, with mobile positioned as the control surface, according to cursor_ai's launch post.
• cursor_ai's thread says cloud environments now save as snapshots, which cuts repeated setup time and lets agents keep testing changes until output is verified.
• Cursor also added /in-cloud, a command that starts a subagent in its own cloud VM, per cursor_ai's thread, giving long-running or parallel work a separate workspace.
• Early reaction centered on setup friction more than the mobile app itself, with mattlam_'s reply calling environment setup the main cloud annoyance Cursor addressed.

cursor_ai's launch post frames the update around a simple handoff: start local, move to cloud, check back from your phone. cursor_ai's follow-up thread adds the more useful implementation detail, snapshots and isolated cloud VMs. Even ericzakariasson's post is really about that workflow change, while ericzakariasson's reply notes mobile is not limited to cloud sessions.

Cursor's headline feature is continuity. A local agent can move to the cloud and keep working when the laptop is closed, then return a PR and demo when it's done.

The mobile app matters here as the handoff layer, not just a companion client. ericzakariasson's post says the app is nearing GA, which lines up with Cursor pushing phone-based prompting in the launch copy.

The thread's second reveal is the real product change: Cursor says cloud environments are now saved as snapshots, so future agents boot faster in the same environment.

That gives cloud runs a memory of their setup state. Cursor also says agents can keep testing changes until output is verified, which pushes these sessions beyond fire-and-forget background jobs.

Cursor also introduced /in-cloud, which starts a subagent inside its own cloud VM.

Cursor describes two concrete uses:

• isolating long-running work from the local machine
• running parallel work without cluttering the local workspace

That matches mattlam_'s reply, which argued the bigger update was reducing the setup pain that made cloud use annoying in the first place.

One small but useful clarification came in replies. When asked whether the mobile workflow only talks to cloud agents, ericzakariasson's reply said it can connect to local as well.

That means the mobile app is doing double duty: cloud handoff for long runs, and remote access into a local session when the machine is still reachable.