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 Can Now Run on Self-Hosted Infrastructure(4 posts)→
More from coding & agent
- Firecrawl open-sources anydoc: Rust library converts Word, PPT, Excel, PDF to Markdown in milliseconds — tom_doerr · 2026-09-03
- Tsinghua's Frontis-MA1 pushes 35B model to 71.21% on MLE-Bench Lite for recursive self-improvement — ceciletamura · 2026-09-03
- Codex Remote syncs queued messages, no longer needs iOS app in foreground — Dimillian · 2026-09-03
- Fully automated tracker discovers new Hugging Face models within a day and estimates max tok/s — helloiamleonie · 2026-09-03
- Clearing ~900 accumulated chats made Codex feel instantly lighter — CtrlAltDwayne · 2026-09-03
- Radix sort in pure fragment shaders: 5B key/value pairs/sec with zero compute shaders — Michael_Moroz_ · 2026-09-03