2 min lesson

Cloud subagents

Complete "Cloud subagents". Check the final state against the lesson before you move on.

Check your understanding

Fan out two independent tasks with /in-cloud, then merge one at a time.

Outcome: One PR reviewed and merged at a time: the work fanned out in parallel, but each change still landed through its own review gate.

Fan out two independent tasks with /in-cloud, then merge one at a time

Cloud subagents

SayI've got two unrelated chores — bump the linter config and add a health-check endpoint. They don't touch the same files, so I want both running while I stay on the main agent.

Type/in-cloud bump the linter config to the new ruleset

DoSubmit the first task with /in-cloud.

SeeCursor spins up a cloud subagent in its own VM and branch for that task and runs it in the background, so your parent agent is never interrupted.

Type/in-cloud add a /healthz endpoint that returns the build SHA

SeeThe second subagent gets its own VM and branch too, so the two runs can't collide on files or history.

Type/babysit

DoWhen the linter PR is close, use /babysit (or the quick-action pill) on it.

SeeA cloud subagent babysits that PR and iterates remotely to get it merge-ready, so you're not hand-holding every step.

DoReview and merge the linter PR on its own, then come back to the health-check PR and do the same.

SeeOne PR reviewed and merged at a time: the work fanned out in parallel, but each change still landed through its own review gate.

Learn more

Optional practice

Practice: Cloud subagents

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