《Cursor Docs》-Team Pools
A pool is a named routing target that connects requests with Self Hosted Machines workers. Requests wait in the pool until an available worker claims them. Create separate pools for different execution environments, such as gpu for work that needs GPUs or ios for work that needs a Mac.
Read More《Cursor Docs》-My Machines
My Machines is the personal Self Hosted Machines configuration. It lets a specific user run Cloud Agent tool calls on a machine they already use: a laptop, devbox, or remote VM. Use it when that machine is the desired execution environment for a repo.
Read More《Cursor Docs》-Integrations
Run Team Pool workers on an infrastructure partner's platform, or start from a reference template you clone and adapt. Every option runs the same worker: the Cursor CLI opens an outbound HTTPS connection to Cursor, and Cursor sends agent tool calls over that connection.
Read More《Cursor Docs》-Computer use and desktop sharing
Computer use lets an agent on a Self Hosted Machines worker click, type, take screenshots, and drive applications with a UI. Agents can also drive a browser when the worker has Chrome or Chromium installed. It works on macOS and Linux workers, for both My Machines and Team Pools. Desktop sharing lets authorized viewers watch or take control of a Linux agent desktop from Cursor. For the product behavior on managed Cloud Agents, see Capabilities.
Read More《Cursor Docs》-Choose where Cloud Agents run
Cursor hosted Cloud Agents run each agent in an isolated cloud VM with managed lifecycle, saved environments, artifact capture, and dashboard controls for secrets and network access.
Read More《Cursor Docs》-Cloud Environment Setup
Cloud agents run on isolated Ubuntu machines. Configure the environment so the agent has the same repos, tools, dependencies, secrets, and network access a developer would use.
Read More《Cursor Docs》-Cloud Agents settings
Workspace admins can configure Cloud Agents from the Cloud Agents dashboard.
Read More《Cursor Docs》-Governed Cloud Agents for private code and internal services
Coding agents that work on private code have to clear a specific bar: source that can't leave your network, a compliance perimeter to honor, access and network policy you control, and a setup that fits the infrastructure you already run.
Read More《Cursor Docs》-Secrets & Network
Cloud Agents are available in Privacy Mode. We never train on your code and only retain code for running the agent. Learn more about Privacy mode.
Read More《Cursor Docs》-Security overview
This page explains how Cloud Agents are built and secured. It walks through what happens when an agent runs, how access is granted, where the code and data live, how they're isolated and encrypted, and what controls you have over each stage. It answers the questions that come up when a team evaluates Cloud Agents against its security requirements.
Read More《Cursor Docs》-Private Connectivity
Cursor supports private network connectivity for Enterprise teams that need Cursor to work with systems that are not reachable from the public internet. This includes self hosted GitHub Enterprise Server, GitLab Enterprise, Bitbucket Data Center, Artifactory, Nexus, private source control APIs, and webhook traffic from those systems back to Cursor.
Read More《Cursor Docs》-Cursor for iOS
Cursor for iOS is in beta. Features may change before general availability.
Read More《Cursor Docs》-Agent metadata
Agent metadata is in preview and subject to change, including breaking changes.
Read More《Cursor Docs》-OIDC tokens
Cloud Agents can mint short lived OIDC JWTs from inside the VM and use them to assume cloud roles or call internal services without storing long lived credentials in Secrets.
Read More《Cursor Docs》-Cloud Agent Builds
Builds prepare your Cloud Agent environment in the background. Each agent starts from a pre built machine with your repositories, tools, and dependencies ready.
Read More《Cursor Docs》-Best Practices
Use these recommendations to get more reliable Cloud Agent runs.
Read More《Cursor Docs》-Automations
Cursor Automations run cloud agents in the background, either on a schedule or in response to events from GitHub, GitLab, Slack, webhooks, Linear, and more.
Read More《Cursor Docs》-Webhooks
When you create an agent with a webhook URL, Cursor will send HTTP POST requests to notify you about status changes. Currently, only statusChange events are supported, specifically when an agent encounters an ERROR or FINISHED state.
Read More《Cursor Docs》-Cloud Agents API
The Cloud Agents API v1 is in public beta. APIs may change before general availability.
Read More《Cursor Docs》-Cloud Agents
Cloud agents use the same agent fundamentals but run in isolated VMs in the cloud with full development environments instead of on your local machine. The development environment is similar to the setup on your laptop: cloned repos, installed dependencies, secrets, startup commands, and network access.
Read MoreWarp Releases Standalone Agent CLI: Multi-Model Programming Agent Available Across Any Terminal
On August 4, 2026, Warp officially released Warp Agent CLI, spinning off the multi-model programming Agent originally built into Warp Terminal into a standalone `warp` command that can be used in any terminal such as Ghostty, iTerm 2 and VS Code. It features built-in task-level model routing, US-hosted open-source weights and custom Router; it is deeply integrated with the Shell based on PTY mux, supports full-screen TUI and SSH remote access without requiring remote installation. Supported by the Oz platform, it enables Cloud Agent handoff and multi-Agent orchestration, and sub-Agents can adopt harnesses such as Claude Code and Codex. It can be installed with a single `curl` command, and inference can be accessed via subscription, on-demand Credits or API Key.
Read More