Cursor 3.7 Adds Cloud Subagents That Run on Their Own VMs

Cursor 3.7, released June 17, ships two new features for running agent work off your local machine: cloud environment setup and cloud subagents. Both are available in the Agents Window.

Cloud Environment Setup

Cursor can now configure a development environment in the cloud from scratch in under ten minutes. You define your environment in .cursor/environment.json, and Cursor handles the setup, capturing the result as a reusable snapshot. Future cloud agents start from that snapshot instead of repeating setup from zero, which also means teams can share a consistent baseline.

The setup runs in a shared terminal session, so you can watch the agent install dependencies and handle configuration in real time before it gets captured.

Cloud Subagents with /in-cloud

The bigger addition is the /in-cloud command. From any agent session, you can type /in-cloud to spin up a subagent that runs on a dedicated VM with its own branch. The primary session keeps running while the cloud agent works separately.

Cursor describes it directly: “It runs on its own VM and branch, so your local workspace stays clean and responsive.”

The use cases are mostly things that don’t need your attention while they run: fixing CI failures, exploring an unfamiliar codebase, running a long refactor, or anything where you’d rather not tie up your local environment. You can kick off as many cloud agents in parallel as you need.

/babysit for PRs

A related command, /babysit, targets pull request preparation specifically. You ask a cloud subagent to babysit a PR, and it iterates remotely to get it into a mergeable state. No local session required. You can trigger it from a quick-action pill or by typing the command directly.

Local-to-Cloud Handoff

Sessions can also transfer between local and cloud environments more reliably than before. If you start a task locally and want to hand it off to a cloud agent, or retrieve cloud work locally for testing, the handoff is cleaner in this release.

Cloud subagents run in the background without blocking the parent agent, so you can offload intensive or slow work and continue with whatever you were doing.

Source: Cursor 3.7 changelog