Cursor just launched Origin to host your code with built-in agents

There is no better day to launch a direct competitor to a legacy platform than the exact morning that legacy platform crashes into the ground.

Cursor just rolled out Origin, a new native code-hosting platform now available in early beta for all paid plan subscribers. In an unbelievable stroke of timing, the launch landed right in the middle of a massive global outage at GitHub, which suffered degraded services for over six hours and saw error rates hover near twenty percent worldwide.

Now, the AI coding company is officially stepping directly into Microsoft's front yard.

Git hosting built for autonomous agents

Origin covers the developer essentials from day one: code repos, pull requests, in-browser code review, and live GitHub synchronization.

When developers create a brand-new repository on Origin, it lives under a custom codebase domain, turning Cursor into the primary source of truth where pushes land directly without touching third parties.

However, Cursor is not asking anyone to quit GitHub cold turkey. Synced repos let teams connect their existing GitHub organizations and mirror projects in real time.

For these synced projects, GitHub remains the underlying source of truth, but PR comments, checks, and code merges sync bidirectionally within seconds. You can review a teammate's PR on Cursor and have your remarks instantly show up on GitHub.

The real hook here is Cursor’s agent. Instead of jumping out of the editor to open a browser tab, you can ask the agent questions right inside the repo you are browsing, instruct it to push branch changes, or let it patch pull requests automatically.

Cursor also announced Day 1 integrations with Vercel for instant PR preview deployments, alongside Depot and Buildkite, which can run existing GitHub Actions workflows without requiring teams to rewrite their build pipelines.

Why it matters

Cursor’s move into code hosting is an aggressive bid to own the entire developer surface area.

For engineers and small product teams, there is no need to migrate your production repositories outright just yet. But turning on GitHub sync is an absolute no-brainer. Having your code, terminal agents, review cycles, and preview deployments living inside the same unified canvas shaves off endless context-switching overhead.

For the wider tech landscape, this marks the first real existential threat to GitHub's two-decade hegemony. GitHub boasts roughly 180 million users, but it has suffered from escalating reliability headaches, logging over 250 outages across the past year according to industry trackers. When a legacy titan stumbles, users look for an escape hatch.

Cursor's strategy is brilliant because it lowers switching friction through bidirectional sync, quietly making GitHub an invisible commodity backend. The big question mark is enterprise infrastructure trust. Handling enterprise-grade access control, uptime, and compliance is a grueling slog, and Cursor will have to prove its rails are truly sturdier than the ones it aims to replace.