---
title: "Run cloud agents in your own infrastructure"
description: "Cursor has made self-hosted cloud agents generally available, allowing code, tool execution, and build artifacts to remain within an organization’s network. Each agent runs in an isolated virtual machine or dedicated worker with a terminal, browser, and full desktop; it can clone repositories, configure environments, write and test code, and push changes for review. A worker connects outbound to Cursor’s cloud over HTTPS, receives tool calls from the agent harness, and returns execution results, while organizations can run long-lived or single-use workers and manage large fleets through a Helm chart, Kubernetes operator, or fleet management API. The product retains cloud-agent capabilities including multi-model support, plugins, and team permissions, while giving teams access to internal caches, dependencies, endpoints, and security controls without maintaining a separate agent stack."
---

# Run cloud agents in your own infrastructure

[Cursor](https://yomu.fyi/company/cursor) · Katia Bazzi · Mar 25, 2026

**Type:** Announcement

## Summary

Cursor has made self-hosted cloud agents generally available, allowing code, tool execution, and build artifacts to remain within an organization’s network. Each agent runs in an isolated virtual machine or dedicated worker with a terminal, browser, and full desktop; it can clone repositories, configure environments, write and test code, and push changes for review. A worker connects outbound to Cursor’s cloud over HTTPS, receives tool calls from the agent harness, and returns execution results, while organizations can run long-lived or single-use workers and manage large fleets through a Helm chart, Kubernetes operator, or fleet management API. The product retains cloud-agent capabilities including multi-model support, plugins, and team permissions, while giving teams access to internal caches, dependencies, endpoints, and security controls without maintaining a separate agent stack.

## Context

Enterprises in highly regulated environments may be unable to let code, secrets, or build artifacts leave their networks. Some teams also rely on internal caches, dependencies, and network endpoints available only through strictly configured machines, leading them to build and maintain their own background coding agents.

## Approach / What changed

Self-hosted cloud agents keep execution in the organization’s infrastructure while Cursor handles orchestration, model access, and the user experience. An outbound HTTPS worker receives tool calls from Cursor’s agent harness and returns results; each session gets a dedicated worker, with fleet scaling available through a Helm chart, Kubernetes operator, or fleet management API.

## Takeaways

- Workers connect outbound via HTTPS, so self-hosted agents require no inbound ports, firewall changes, or VPN tunnels.
- Each agent session receives a dedicated worker that can be long-lived or single-use, supporting parallel workloads without machine sharing.
- Organizations can scale workers with a Kubernetes WorkerDeployment or use the fleet management API to monitor utilization and build autoscaling on other infrastructure.

**Tags:** [Cursor](https://yomu.fyi/topic/cursor), [Kubernetes](https://yomu.fyi/topic/kubernetes), [Security](https://yomu.fyi/topic/security)

- Source: [Cursor](https://cursor.com/blog/self-hosted-cloud-agents)
- Source URL: https://cursor.com/blog/self-hosted-cloud-agents
- Ingested by Yomu: 2026-09-02T11:43:36.176Z

[Read original post](https://cursor.com/blog/self-hosted-cloud-agents)