Cursor launches Self-Hosted Machines: cloud-hosted agents run on your own servers
xiaohu · x · 2026-09-03
Cursor introduced Self-Hosted Machines, letting Cloud Agents execute files, terminal commands, browser control and local MCP calls on company-owned machines while the agent loop, planning and model inference stay in Cursor's cloud.
- Previously Cloud Agents ran on Cursor-managed remote VMs; execution can now move to intranet servers, corporate cloud hosts, Macs, GPU machines or local devices
- Targets three needs: tasks that must run inside the corporate network, internal system access, and Mac/GPU/special build environments
- Local workers only need outbound HTTPS connections—no inbound ports, public IPs or VPN—but code content, terminal output, diffs and screenshots may still be sent to Cursor
- Setup is agent worker start via the Cursor CLI; offerings include My Machines (personal devices) and Team Pools (shared, scalable capacity)
- Cursor says over 60% of its internal merged PRs are now created by cloud agents (self-reported)
Related event: Cursor Cloud Agents Now Run on Self-Hosted Infrastructure(6 posts)→
More from coding & agent
- Screenshot table to Excel in PowerShell: LLM only locates, code does the rest — dfinke · 2026-10-21
- One line of PowerShell turns any screenshot table into real Excel data in 4 seconds — dfinke · 2026-10-21
- Screenshot to spreadsheet in 4 seconds with one line of PowerShell — dfinke · 2026-10-21
- A mitm proxy that rewrites robots.txt to Allow: all gets you really far — generativist · 2026-10-21
- Anaconda ships MCP to stop coding agents from hallucinating malicious dependency packages — anacondainc · 2026-10-21
- 5-person team uses Claude and 300+ agents to design 318,484 proteins in 64 hours — 141_1337 · 2026-10-21