Cursor spent August turning an editor into infrastructure. Three releases, and together they describe a clear direction.
Origin: Cursor hosts your code
On August 17 Cursor launched Origin, built-in code repository hosting, in early beta. It syncs with GitHub repositories bidirectionally in real time, manages pull requests with GitHub sync, and integrates with Vercel, Depot and Buildkite.
An AI editor shipping its own code host is a significant move. It means the agent no longer has to reach across an API boundary to read history, open branches or manage reviews.
Agents without a repository
On August 27 Cloud Agents stopped requiring GitHub or any third-party version control to begin work. An agent now creates an Origin repo in the background, and the work can be converted to a permanent repository later with a chosen name and visibility. Live browser preview and Vercel publishing are included.
This removes the setup step entirely: describe a task, get working code with history, decide afterwards whether it deserves to be a real project.
Self-hosted machines
On September 2 Cursor added self-hosted machines, keeping tool execution inside your own network. There are personal machines and team pools, computer use on Linux and Mac with desktop control, and support for AWS Lambda, Coder, Cloudflare, Daytona and Modal.
That is the enterprise unlock. Plenty of organisations cannot let an agent execute code on a vendor's infrastructure, and this addresses that objection directly.
Why it matters
Read together, these three changes move Cursor from "AI features in an editor" to a place where code lives, runs and ships. Which also means the switching cost is climbing: a repo in Origin, agents configured around it and execution on your own machines is a much deeper commitment than an editor you can swap.
Worth weighing before adopting Origin as anything other than a mirror. Bidirectional GitHub sync makes that easy to do safely — keep GitHub authoritative and let Origin be the working copy.