Cursor
@cursor_ai
Cursor cloud agents can now run on your infrastructure. Get the same cloud agent harness and experience, but keep your code and tool execution entirely in your own network. https://t.co/u3iVnZxtKV
55retweets
View on XCursor Cloud Agents Now Run on Your Own Infrastructure
Cursor· Updated
Cursor has made self-hosted cloud agents generally available, letting enterprise teams run autonomous coding agents entirely within their own network. Regulated organizations that previously couldn't use cloud agents due to compliance rules now have a path to adopt them.
Cursor has made self-hosted cloud agents generally available. The same agents that clone repos, write and test code, and push pull requests — each in an isolated VM — can now execute on a team's own infrastructure. A worker connects outbound via HTTPS to Cursor's cloud for orchestration; no inbound ports or firewall changes required. Code, secrets, and build artifacts stay inside the team's network.
This resolves a compliance wall that blocked many regulated enterprises. Financial services firms with strict security models couldn't allow code to leave internal machines — so cloud coding agents were off limits. The split keeps Cursor handling inference and planning while execution, internal caches, and network endpoints remain inside the team's environment.
Self-hosted agents are live in the Cursor Dashboard. For larger deployments, a Helm chart and Kubernetes operator let you define a WorkerDeployment pool with automatic scaling. Non-Kubernetes environments use a fleet management API.
Every HeadsUpAI update is written based on its original source and reviewed before it's published. Read our editorial standards →
