Skip to lesson
Exit
Hand work between local and cloud1 / 2

2 min lesson

Hand off the payment suite

Push one payment refactor, run its long suite in cloud and inspect the returned branch locally.

Step 1 of 2

Use payments/refactor-tax at commit 81f4c2a. Confirm that the branch is pushed, choose it as the cloud starting ref and state the payment-only change boundary. When the run returns, review the suite output and draft pull request, fetch its separate branch, inspect the diff and rerun the local typecheck and targeted payment test.

Hand the rest of the run to a cloud sibling

0:52 · narrated
Read this demo as text
  1. The local session already finished the refactor — typecheck green. What's left is the 40-minute integration suite, and that shouldn't tie up this machine.
  2. Switch to the cloud sibling in the sidebar — queued on the same branch, ready for the part that needs a machine, not a person watching it.
  3. Send it. The cloud sibling picks up the branch in its own isolated VM — local and cloud stay on the same history instead of drifting apart.
  4. Suite green in the cloud VM. Changes panel opens on the same branch you refactored locally — nothing diverged.
  5. Checks are green on the PR. Pull the branch back locally and run what the suite can't see — a type check, a read through the diff — before you merge.
Keep local work for the edit, then switch to a cloud sibling on the same branch for the long suite and PR.

Practice next: Split a stuck local run: keep the edit local, hand the long verify to a cloud session on the same branch.

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