[ ABORT TO HUD ]
SEQ. 1

Autonomous Cloud Workflows

🌐 Cloud Agents 22 min 600 BASE XP⌨ HANDS-ON LAB

Coding While You Sleep

Cloud Agents (formerly "Background Agents") run in isolated virtual machines in the cloud, each with a full development environment. They clone your repo, write code, run tests, and open pull requests - while you keep working, or while you're away entirely. You can run an unlimited number in parallel, including several on the same task to compare approaches.

Kick Off From Anywhere

Entry PointHow
EditorCloud dropdown in the agent pane - or prefix any prompt with & for instant cloud handoff
Webcursor.com/agents - manage your fleet from any browser
iOS & iPad appKick off and monitor agents from your phone or tablet; Live Activities, an Inbox, full PR review (comments, checks, approvals), Bitbucket & Azure DevOps support, and multi-PR sessions (all paid plans)
SlackMention @cursor in a thread to spawn an agent with the discussion as context
GitHub / BitbucketComment @cursor on an issue or PR
Linear & APIDelegate issues to Cursor, or drive agents programmatically

Environments & Self-Hosted Machines (September 2026)

Each agent's VM is configured via .cursor/environment.json - let the agent set up its own environment interactively, snapshot the result, or supply a Dockerfile for fully reproducible installs (deps, secrets, services). Local ↔ cloud handoff works in both directions, and cloud agents can spawn subagents (/in-cloud) or babysit a PR through CI (/babysit).

Self-Hosted Machines (September 2, 2026)

For regulated enterprise codebases, Cursor introduced support for Self-Hosted Machines. Tool executions, bash commands, and desktop/browser "computer use" run on your private corporate hardware (Linux or macOS), ensuring source code and secrets never leave your private VPC or internal network.

Start from Scratch & Cursor Origin (Late August 2026)

Cloud Agents no longer require a pre-existing GitHub repository. You can start prompting immediately from scratch; the agent boots an environment, initializes a repository on Cursor Origin, and provides live port forwarding for instant browser preview and one-click Vercel deployments.

Artifacts & Remote Control

Cloud agents produce artifacts - screenshots, videos, and logs of what they built and tested - and you can take remote desktop control of the agent's VM to inspect or intervene directly.

Automations: Always-On Agents

Automations are scheduled or event-triggered cloud agents: nightly dependency updates, triaging fresh GitHub issues, responding to a Slack emoji, and more. Create one with the /automate skill.

SOE & AOE Operational Runbook for Cursor

  • SOE Standard: Commit modular rules in .cursor/rules/*.mdc with strict glob targeting; commit .cursor/environment.json to guarantee identical container dependencies across local and cloud agents; add sensitive secrets to .cursorignore.
  • AOE Harness: Pair Cloud Agents with Bugbot merge gates on PRs; deploy Self-Hosted Machines for sensitive databases and internal APIs; configure usage limits to manage Max Mode context billing across team fleets.
Billing Note: Cloud Agents always run in Max Mode (maximum context window) and are billed at API pricing - budget accordingly for large fleets.
⌨ HANDS-ON LABDrive Cursor from the Terminal
⭐ +200 XP

Cursor's CLI puts the agent in your terminal - perfect for scripts and CI. Install it, start an interactive session, then run a headless prompt.

1Install the Cursor CLI with the official install script (curl piped to bash).
2Start an interactive agent session in your terminal.
3Run it non-interactively for CI: print mode with the -p flag.
lab-sandbox — simulated environment
INFINITY LAB SANDBOX v2.6 — simulated shell
Type the command for the current objective. Helpers: "hint", "solution", "clear".
$
OBJECTIVE 1 / 3 — type "hint" if stuck
SYNAPSE VERIFICATION
QUERY 1 // 5
How many Cloud Agents can you run simultaneously?
1
Up to 8
Unlimited - including several on the same task to compare approaches
One per repo