Cloud Agents
Cloud Agents run in isolated cloud environments instead of on your local machine.
What can Cloud Agents do?
Cloud Agents handle coding tasks without you needing to be in the loop. They can build features, fix bugs, write tests, open PRs, and share a video of it working. Each task starts from a configured cloud environment with the repos, dependencies, secrets, and network access the agent needs.
Cloud Agents can also use multi-repo environments. This lets one agent work across frontend, backend, infrastructure, or shared-library repos in the same run.
How does "Move to Cloud" handle my file state?
"Move to Cloud" does not snapshot your local uncommitted changes. The cloud agent starts from a clean git state on the remote repository. It transfers your conversation history and context, but not dirty files or uncommitted edits. Commit or stash your changes before moving a conversation to the cloud if you want the agent to work from your latest state.
Can Cloud Agents test my app in a browser?
Yes. Each cloud agent runs in its own isolated VM with a full desktop environment. Agents use a mouse and keyboard to control the desktop and browser, the same way a human developer would.
This means agents can start dev servers, open the app in a browser, click through UI flows, and verify their changes work before pushing a PR.
How do Cloud Agents show their work?
Agents attach screenshots, videos, and log references to the PR so you can validate changes without checking out the branch.
Can Cloud Agents use MCP tools?
Yes. Add and manage MCP servers through the MCP dropdown at cursor.com/agents. This gives agents access to databases, APIs, and third-party services during their runs.
Cloud agents support HTTP and stdio servers, plus OAuth for servers that need it. See the Cloud Agent capabilities page for setup details.
Do Cloud Agents run hooks?
Yes. Cloud Agents run command-based hooks from .cursor/hooks.json in your repository. On Enterprise plans, they also run team hooks and enterprise-managed hooks.
Supported hooks include beforeShellExecution, afterShellExecution, beforeReadFile, afterFileEdit, preToolUse, postToolUse, postToolUseFailure, subagentStart, subagentStop, and preCompact.
Some hooks are not available in cloud agents. IDE-specific hooks like Tab hooks and workspaceOpen don't apply. Hooks tied to session lifecycle (sessionStart, sessionEnd, beforeSubmitPrompt) can't run because the cloud VM doesn't exist when the session begins on cursor.com/agents. Prompt-based hooks also aren't supported in cloud agents. User-level hooks from ~/.cursor/hooks.json aren't loaded since the VM doesn't have access to your local configuration.
See the full hooks support matrix for details.
Can Cloud Agents fix CI failures?
Yes. Cloud Agents automatically try to fix GitHub Actions failures on PRs they create. They ignore checks that are also failing on the base branch. This is currently available on Teams plans.
To disable this on a specific PR, comment @cursor autofix off. To re-enable it, comment @cursor autofix on. You can also disable it globally from Cursor Dashboard > Cloud Agents > My Settings.
What do I need to use Cloud Agents?
Cloud Agents are available on all paid Cursor plans.
How do I set up Cloud Agents?
Create a new environment in your Cloud Agents dashboard. You'll connect your GitHub or GitLab account, select one or more repositories, add secrets or environment variables, and verify the setup. See the full setup guide for multi-repo environments, environment-scoped secrets, network access, and Dockerfiles.
How do I start a Cloud Agent task?
- In Cursor: Select Cloud in the dropdown under the agent input
- On the web: Go to cursor.com/agents
- Via Slack: Use @Cursor
- On GitHub: Comment @cursor on a PR or issue
- In Linear: Use @Cursor on an issue
- Via API: Use the Cloud Agent API
How is Cloud Agent usage priced?
Cloud Agents are charged at API pricing for the selected model. Only Max Mode-compatible models are available.
Can I run Cloud Agents automatically or on a cron?
Yes. Use Automations to run Cloud Agents on a schedule or from events in GitHub, Slack, Linear, PagerDuty, or webhooks. Set them up at cursor.com/automations. See the automations docs for trigger types and templates.
Does Privacy Mode work with Cloud Agents?
Yes. Cloud Agents are available with Privacy Mode. See the Cloud Agent security page for details.