Cursor Launches Origin, a GitHub-Rival Code Host

Cursor just crossed the line from editor to forge: on August 17 it began rolling out Origin, a code-hosting platform with repositories, pull requests, and GitHub sync, in early beta for all paid users. It's a credible first swing at GitHub — but it ships with no published retention, residency, or training-use terms, and it's on by default. Treat it as a GitHub companion, not a migration target.

What happened

Origin lives in a new Codebase tab inside Cursor: name a codebase, create repos, push from a CLI, and get pull requests with timelines, commits, checks, and inline review — no browser tab needed. It launched with three day-one integrations: Vercel (preview deployments per PR), plus Depot and Buildkite for CI, both running existing GitHub Actions workflows unchanged.

GitHub sync is the design centerpiece, not a hard break. "Your GitHub repos can sit alongside the ones Cursor hosts," Cursor's changelog reads — connect a GitHub org, pick repos, and "pushes keep going to GitHub, which stays the source of truth for anything started there." PR conversations sync both ways within seconds.

Origin runs on Graphite, the code-review startup Cursor acquired in December 2025, and Cursor says "agent-native" features and a wider app ecosystem are next.

The timing was loud. Origin rolled out the same morning GitHub logged a 6-hour-42-minute global degradation — error rates near 20% across pull requests, issues, and the API, near 50% on archive and raw-file downloads, with Copilot and enterprise SSO down too (GitHub's incident log, via VentureBeat).

Why Origin matters

Cursor now owns the editor where agents write code, the host where it lives, and — through its frontier-model access — part of the model layer agents run on. That's a bigger slice of the stack than any AI-coding tool has claimed, and it lands while GitHub is reeling: 257 incidents from May 2025 to April 2026, 48 major, per a LeadDev analysis (via VentureBeat).

It's a smart wedge, not a rip-and-replace. Because GitHub stays the source of truth, a read-mostly mirror costs nothing to try and quietly relocates where developers spend their hours. Cursor stays conditional in our directory — the most polished AI editor, but SpaceX's $60 billion acquisition (closed August 15, days before Origin) raises a governance question Cursor hasn't answered in writing: who holds your code, and what may they do with it.

What changes for you

If your org pays for Cursor, check the admin posture now: Origin is on by default unless an enterprise admin opts out, which means a decision about mirroring proprietary code may already have been made for you. Confirming it is a Monday-morning task, not a next-quarter one.

Until Cursor publishes retention, residency, training-use, and subprocessor terms, treat Origin as a convenience layer over GitHub — which is exactly what its architecture is. A product page is not a contract.

FAQ

Do I have to leave GitHub to use Origin? No. Connect a GitHub org, pick repos, and they sync into Origin while GitHub stays the source of truth. Permissions mirror GitHub's existing read/write settings.

Is my code now hosted by Cursor (and SpaceX)? Only repos you create or sync in Origin. Origin is opt-out on paid plans, so check your org's posture — retention, residency, and training-use terms are not yet published.

Does Origin run my existing CI? Yes for GitHub Actions — Depot and Buildkite both execute existing workflows unchanged, and Vercel adds preview deployments per PR.