Cursor just shipped version 3.7, and the headline feature is deceptively simple: moving a coding agent from your laptop to the cloud is now a one-click operation. But underneath that convenience is a meaningful shift in how the tool thinks about where work happens, and how much of it can run without you.
The local-to-cloud handoff problem
Running agents locally has always had a ceiling. Local agents quickly run into conflicts and compete with each other, and with you, for your computer's resources. The more tasks you throw at them, the more your machine slows down. Cursor's answer has been cloud agents for a while now, but the friction of getting there was real. This update removes most of it.
The release introduces updates to cloud agents in the Agents Window of the Cursor desktop app, covering three main areas: cloud environment setup, cloud subagents with /in-cloud, and more reliable handoff between local and cloud sessions.
Spin up a subagent with one slash command
The most immediately useful addition is /in-cloud. Typing /in-cloud spins up a cloud subagent in its own VM to work on the next task you submit. It runs on its own VM and branch, so your local workspace stays clean and responsive.
This is not just offloading work, it is a proper isolation primitive. The subagent gets its own branch and environment, completely separate from whatever you are doing locally. It is especially useful for isolating long-running or parallel work like fixing CI, investigating an issue, or exploring a codebase while you keep working locally.
Don't miss what's next in AI
Join 300,000+ engineers and researchers who get the signal, not the noise.
- Full access to in-depth AI research breakdowns
- Be the first to know what's trending before it hits mainstream
- Daily curated papers, repos, and industry moves