Skip to content

Guide

Cursor Cloud Agents Guide

By The Learn Cursor Editorial TeamUpdated 3 sections

Answer first

Cursor's June 2026 Cloud Agents update added guided cloud environment setup, reusable snapshots, .cursor/environment.json, /in-cloud subagents, /babysit for PR supervision and more reliable local/cloud handoff.

Cover image for Cursor Cloud Agents Guide

What changed in Cursor Cloud Agents, June 2026?

Cursor's June 2026 Cloud Agents update added guided cloud environment setup, reusable snapshots, .cursor/environment.json, /in-cloud subagents, /babysit for PR supervision and more reliable local/cloud handoff.

Release fact
Cloud setup
Why it matters
Cursor can help set up a cloud development environment in less than 10 minutes.
Release fact
Reusable snapshots
Why it matters
Working environments can be captured so future cloud agents boot faster and can run software.
Release fact
/in-cloud
Why it matters
A cloud subagent runs the next task in its own VM and branch.
Release fact
/babysit
Why it matters
A cloud agent can keep iterating on a PR until it is closer to merge-ready.
Release fact
Handoff
Why it matters
Work can move from local to cloud and back while preserving branch and verification context.

Release facts checked on 2026-06-23. Use the linked Cursor sources before quoting product mechanics in a live customer, security or pricing conversation.

How should a team use Cursor Cloud Agents?

  1. 1Use local Agent or Plan Mode for ambiguous work that needs close supervision.
  2. 2Set up a cloud environment with install, start and verification commands before delegating long work.
  3. 3Launch /in-cloud only for tasks with separate branch boundaries and low conflict risk.
  4. 4Pull the result back locally and rerun the checks a human reviewer would trust.
Release-to-workflow map

Interactive diagram. Use Tab to move through hotspots or use the step controls when shown.

Step 1Step 2Step 3Step 4▲ GATE
1/4
Step 1: Use local Agent or Plan Mode for ambiguous work that needs close supervision.

What should stay bounded?

Guardrail

Do not send work to cloud until the environment can actually install, start and test the repo.

Guardrail

Use separate branches for parallel agents and review one output at a time.

Guardrail

Keep sensitive or high-blast-radius work local unless the data-flow and secret boundary are approved.

Frequently asked questions

Who is Cursor Cloud Agents Guide for?

Developers and platform teams deciding when work should run locally, in a cloud agent or in parallel cloud subagents.

What makes this page credible?

The guide uses Cursor's June 17, 2026 changelog and cloud-environment blog to separate setup, delegation and handoff.

What should I do next?

Start with one real repo task, capture the prompt and review the result before scaling the workflow.

Editorial notes

Source review

Last checked
June 23, 2026
Scope
Cursor docs, Cursor Learn pages and product docs.
Refresh
Quarterly, plus changes to Cursor agent or CLI docs.
Reviewer
Learn Cursor editorial

Page assets

Primary media
Workflow diagram.
Supporting media
Learn Cursor practice screenshot.
Interactive element
Step diagram.
Transcript
Add a transcript when a recorded walkthrough is added.
Refresh owner
Learn Cursor editorial.

Content pod

Pod
Workflow pod
Owner
Editorial director
Reviewers
DevRel engineer, SEO lead, Senior editor

QA gate

Human signal
Includes a task-specific diagram, checklist or calculator.
Claims
Claims stay tied to sources, visible limits and page scope.
Visual proof
Uses product screenshots or annotated workflow diagrams, not stock art.
Page rhythm
Sections vary between answer, method, visual and action blocks.

Sources & last verified

Cursor ships frequently. Facts verified against primary sources on June 23, 2026.

Keep reading