Cloud Agents

Cloud Agents (formerly called Background Agents) run the same agent on isolated virtual machines in Cursor's cloud instead of your computer. Each gets a full development environment: your repository cloned, dependencies installed, secrets and network access. Because they don't depend on your laptop, several can work in parallel and keep going while you're offline.

Ways to start one:

• in Cursor, choose Cloud in the dropdown under the agent input,
• on the web at cursor.com/agents (also usable from a phone),
• by mentioning @cursor in Slack, Linear, or a GitHub or Bitbucket issue or PR comment,
• through an API.

An admin first connects your source control (GitHub, GitLab, Bitbucket Cloud or Azure DevOps). The agent works on its own branch, pushes changes and opens a pull request, often with screenshots, videos or logs of what it did. You review it like any PR, and you can take over its remote desktop to test.

The environment can be set up by the agent, from a saved snapshot, or from a Dockerfile referenced in .cursor/environment.json. Secrets are added in the dashboard and injected at start. You can restrict which outbound domains agents may reach.

Things to keep in mind: Cloud Agents need a paid plan and are billed at API rates for the chosen model, so set a spend limit; they don't ask for approval for commands (run modes are local only), so restrict network access and secrets to what tasks need; and treat their PRs with the same review and CI checks as human ones.