Skip to lesson
Exit
Cloud Agent Basics1 / 2

2 min lesson

Cloud Agents

Explain the practical point behind "The case: you can choose local Agent, worktree, Cloud Agent or cloud subagent deliberately."

Step 1 of 2

The case: you can choose local Agent, worktree, Cloud Agent or cloud subagent deliberately. Start with this check: The cloud agent has repository and environment access. Walk it once against a real situation so you can defend the call, not just assert it.

Cloud Agent opens the PR

0:40 · narrated
Read this demo as text
  1. This prompt asks for a pull request when the work is ready. Not a merge. Send it on a Cloud Agent so it runs in an isolated VM, on its own branch, while you keep moving.
  2. And boom, the remote build lands. Three files in the file components/search, Changes panel open. Your machine stayed free the whole time. That is the point of shipping the work to the cloud.
  3. Green checks on the PR tab. Read the diff, then merge it yourself. Cloud Agents hand you proof. They do not deploy.
Cloud Agent builds in an isolated VM, opens a PR, and leaves the merge to you.

Practice next: Now do the module workflow: launch the Cloud Agent path and stop at the PR — do not merge.

Simulated Cursor 3.12 (macOS, light) — beta educational reconstruction, not the real product.

Learn more

Full explanation

Cloud Agents

Route one background task to a Cloud Agent, then defend the call
Cloud Agents
SayI need to bump our HTTP client one minor version, regenerate the lockfile, and get the full test suite green. Does this belong on a Cloud Agent or do I keep it local?
DoClassify the work before you route it. The output here is a PR that either passes CI or it doesn't, which makes it artifact-verifiable with no judgment calls mid-run. That is the cloud case.
DoOpen the Agents WindowCursor's surface listing your agent runs; open a run to read its diff and search transcripts from the command palette. Press Enter for the full definition., start a Cloud Agent, and pick the repo and model. Give it the branch and PR expectation up front: open a pull request when the suite passes.
SeeThe agent boots its own isolated VM with the repo's environment, so your local machine stays free.
SeeIt bumps the dependency, regenerates the lockfile, runs the suite in the VM, opens a PR, then tears the VM down. The run finished without you steering each step.
DoReview the PR before you merge: read the lockfile diff, confirm the suite is green, then merge it into your branch locally.
SeeThe PR carries the diff and a green suite from a run you never had to babysit. That artifact is your proof the cloud routing was right, something you can point to instead of assert.
Learn more

Optional practice

Practice: Cloud Agents

QYou've applied it. What actually proves the work is done, not just a plausible answer?