Cursor launched Origin, a native code-hosting platform, into early beta on August 17-18, moving the AI coding IDE directly into GitHub's territory. Origin rolls out to paid Cursor users (Pro, Teams, and Enterprise plans) and brings repositories, pull requests, code browsing, review tools, and CI integrations into Cursor's editor environment. Developers can sync GitHub repositories into Origin with GitHub remaining the source of truth; pushes still go upstream, and PR conversations sync bidirectionally. Vercel, Depot, and Buildkite integrations ship on day one.
The strategic angle is that Origin is built for agent scale, not human scale. Inside Cursor, 35% of merged pull requests were already opened by autonomous agents running in cloud VMs—agents that iterate on code, push branches, and open PRs faster than humans review them. GitHub was designed around human cadence: one developer per branch, a few-hour cycle. Origin inverts that: the primary users are software agents; humans become the review bottleneck. That is not a marketing claim; it is a constraint Cursor is engineering around from the ground up.
For deployment architects, the timing is hard to miss: Origin shipped while GitHub suffered a 6.4-hour global outage, its seventh major incident in 15 days. More importantly, Cursor is now backed by SpaceX, which closed its $60 billion all-stock acquisition of Anysphere (Cursor's parent) on August 14. That means the company building an agent-native code platform has access to NVIDIA's compute, SpaceX's infrastructure, and xAI's AI stack. The GitHub moat was always the ecosystem and the 225 million users; Origin's moat is being the only code-hosting platform designed from the start around the assumption that agents, not humans, write most of the code. That is a very different product surface.