Cursor's self-hosted cloud agents are now generally available. A worker process connects outbound via HTTPS — no inbound ports, no firewall changes. Cursor handles inference and planning, sends tool calls to the worker, results flow back. Each session gets its own dedicated worker; Kubernetes operator available for scale.
The practical benefit: agents can access internal caches, dependencies, and network endpoints from a machine you manage. That gives you control over the execution environment, but it does not prove that every prompt, tool result, or diagnostic stays inside your network; verify the product's data flow and policy before sending secrets.
Teams at Brex, Money Forward, and Notion are running this at scale. Notion cited access to more tools more securely as the reason for adopting it over maintaining their own background agent stack. "Agent infrastructure" is now a real architectural decision.