Cloud Agents and development environments

Home Tools Platforms Cursor Cloud Agents and development environments

Prepare a remote repository workspace and review changes before merging.

Coding & development · Documented · Documentation checked 2026-10-04

Cursor editor agents and Cloud Agents; Grok Bot has a separate shared-computer boundary.

Installed client, subscription, organization settings, repository access, and cloud environment determine capabilities.

The worked example is illustrative and has not been tested in a signed-in product account.

What it does and how it connects

Prepare a remote repository workspace and review changes before merging.

Cloud Agents run in isolated development VMs with repositories, dependencies, startup configuration, network access, and scoped secrets. This differs from the local editor’s current files and services. Source-control connection is an account-level setup requirement for repository-backed tasks.

Walkthrough

Use the product named in the access panel. The steps below combine documented controls with the editorial example.

  1. Have an authorized account admin connect the intended source-control provider.
  2. Prepare a reproducible development environment with actual setup and test commands.
  3. Start a narrow Cloud Agent task on the intended repository / branch.
  4. Inspect logs, checks, and resulting branches or pull requests before merging.

Worked example

Use a sample frontend repository to repair an accessible search empty state. Provide acceptance criteria and a working build environment. If a dependent backend is required, identify it explicitly rather than assuming the VM can access your laptop.

In this sample repo, implement the specified search empty state. Preserve data and URLs, make the reset link work with keyboard navigation, and verify the build plus the reported case. Report blocked dependencies. Create a reviewable handoff; do not merge or deploy.

Inspect and verify the result

Check environment setup, branch identity, and actual verification. Test the output against the acceptance criteria. Multi-repository changes need a reviewable diff and tests for each affected repository.

Limits and troubleshooting

Cloud source-control access requires appropriate repo privileges. Network and service availability can differ from local work. A successful remote build is not a production deployment or proof of end-to-end service behavior.

Data, permissions, and actions

Clones, environment secrets, and external tool connections have cloud handling. Grant test-scoped credentials and review provider permissions. Separate repo-write authority from the additional authority needed to publish or alter live infrastructure.

Review, recovery, and operational limits

Use diffs, checks, and checkpoints as complementary evidence rather than automatic acceptance.

Explore Review, recovery, and operational limits

A local UI repair with deliberate recovery

Fix a sample UI problem while preserving unrelated work.

Explore A local UI repair with deliberate recovery

A cloud change with source and environment review

Run a scoped remote task and hand off tested branches or pull requests.

Explore A cloud change with source and environment review

Permissions and meaningful approvals

Decide what a system may read, what it may change, and when someone needs to authorize a concrete action.

Explore Permissions and meaningful approvals

Sources and verification

Documentation checked 2026-10-04. Examples are illustrative unless described otherwise.

Cloud Agents and environments · Cursor

Share this page