New: Governed Cloud Agents for private code and internal services — how Cursor-managed Cloud Agents reach private code and internal services with private connectivity, guardrails, and customer-controlled secrets, without running a worker…
Changelog
Documentation updates
Cloud Agents
New:Governed Cloud Agents for private code and internal services — how Cursor-managed Cloud Agents reach private code and internal services with private connectivity, guardrails, and customer-controlled secrets, without running a worker fleet.
Removed: Self-hosted runtime docs — Choose where Cloud Agents run, My Machines, Private Cloud Workers, Self-Hosted Pool, and Self-Hosted Cloud deploy guides (Cloud Run, Kubernetes).
Cloud Agents overview now centers Cursor-managed runtime and environment controls (secrets, network allowlists, private connectivity) instead of managed vs. self-hosted runtime choice.
Mobile docs no longer cover picking My Machines or Self-Hosted Pool workers; Remote Control is documented as the path to direct your computer from your phone.
Security and network docs no longer recommend My Machines or Self-Hosted Pool for private network access.
Slack integration options for worker, pool, and self_hosted routing are removed.
Cloud Agent API and capabilities docs drop My Machines / self-hosted routing wording (e.g. user-scoped worker tokens, list filters).
SDKs
Python and TypeScript SDK docs no longer present self-hosted pool as a primary Cloud runtime path; pool / machine env targets are described as self-hosted workers you run.
Enterprise & security
BAA eligible services list Cloud Agents only (no separate self-hosted Cloud Agents callout).
Security Agents run on Cursor’s cloud with no additional self-hosted setup documented.
