Last reviewed
Correct answer: B. On a VM of its own with its own branch, leaving your local checkout and current branch untouched.
Explanation
The principle — A cloud subagent moves the task off your machine. Started from a local session, it spins up its own VM and its own branch and works there.
Why the key is correct — With a separate checkout and branch, your files and your current branch stay as they were, and the parent session keeps running while the remote work proceeds.
Why the others are wrong — Nothing is written into your local checkout, so the handoff cannot collide with the edit you are part-way through. The result lands on the cloud branch rather than on whatever you have checked out. And the work runs remotely rather than as a local background process, so your session is never held waiting.
Remember this — Its own VM, its own branch, your workspace untouched.
Sources — Cursor's Subagents documentation.
Sources
“From a local agent session, you can hand off work to a cloud subagent that runs on its own VM and branch.”
Practise 10 questions on this topic
Take Cursor AI Features — Timed Test 1 (10 questions) — scored instantly, explanation for every question, no login.