Route a dependency bump to a cloud agent1 / 2

2 min lesson

Route one dependency bump

Practice Cloud Agents on one real case. Check the result before moving on.

Confirm that the source control provider is connected, acme/api is writable, release is the intended base branch and the api environment is prepared. Check the spend limit. In Cursor Desktop, select Cloud and choose that repository, branch, environment, model and context window. Ask Agent to update @acme/http from 4.2 to 4.3, change only package.json and the lockfile, run the api-client tests and open a draft pull request against release. Tell it not to merge. Open the agent page and verify the environment or Build and separate branch. Review the draft pull request's target, two-file diff, lockfile, tests and artifacts before a person approves or rejects it.

Cloud Agent opens the PR

0:40 · narrated

Read this demo as text

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.
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.
Green checks on the PR tab. Read the diff, then merge it yourself. Cloud Agents hand you proof. They do not deploy.

Cloud Agent works in an isolated VM, pushes a separate branch and opens a draft pull request for human review.

Practice next: Route one bounded dependency bump, then stop at the reviewed draft pull request.

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

Learn more

Full explanation

Repository route, environment evidence, branch, tests, human handoff

Cloud Agent, update one HTTP client and stop at a draft pull request

Repository route, environment evidence, branch, tests, human handoff

SayUpdate @acme/http from 4.2 to 4.3, regenerate the lockfile and run the api-client tests. The work is committed, the environment can run those tests and the result is easy to judge from a draft pull request.

DoConfirm that the Cursor account has a connected source control provider, read-write access to acme/api, a prepared environment and a spend limit.

SeeThe run has the repository and tools it needs before model usage begins.

DoIn Cursor Desktop, select Cloud. Choose acme/api, base branch release, the prepared api environment and the planned model and context window.

SeeCursor provisions an isolated VM, clones the authorized repository and starts from release on a separate branch.

SayChange only package.json and the lockfile. Update @acme/http to 4.3, run the api-client tests and open a draft pull request against release. Do not merge.

SeeThe agent updates the named files, records the test run and attaches its review artifacts to the handoff.

DoOpen the agent page, verify its environment and separate branch, then review the draft pull request's target, two-file diff, lockfile and api-client test output.

SeeThe draft pull request is ready for a person to approve or reject. The run remains available for review or follow-up while VM resources follow their idle lifecycle.

Learn more

Optional practice

Test yourself on Route one dependency bump

QWhich result proves the dependency bump is ready for human review?