On August 17, Cursor officially began rolling out Origin — its own code hosting service, currently in early beta for all paid plans (except enterprise accounts where admins opted out).

Here is the key point to note: Cursor has traditionally been viewed as an AI editor running on top of GitHub repositories. Origin changes that standing; Cursor now wants to be the place where code lives, not just where code is written.

Essentially, Origin provides the baseline feature set of a code hosting platform:

  • Origin Repos — a new Codebase tab to create repos, complete with its own CLI to clone or push. Each codebase has a URL formatted as cursor.com/codebase/tên.
  • Sync GitHub hai chiều — you can pull GitHub repos into Origin, then browse and search the copy. Crucially: for repos originating from GitHub, GitHub remains the source of truth; pushes still go to GitHub, with Origin serving merely as a real-time updated mirror.
  • Pull requests — view timelines, commits, checks, diffs, comments, and merge. On synced repos, comments work both ways: a comment in Cursor posts to GitHub, while reactions/replies on GitHub appear back in Cursor.
  • Agents across all repos — ask Cursor about the code you are reading, and it can answer, edit code, update PRs, or push branches.
  • Apps — an integrated ecosystem, starting with Vercel (preview deployments for each PR), Depot, and Buildkite (running GitHub Actions or native pipelines).

They made it clear that this is merely the foundation: “agent-native” features will arrive later.

This is more than just a new feature. It signals Cursor’s direction and, more broadly, that of an entire generation of AI coding tools.

When an agent needs to read, edit, inspect, and then merge code, having the code reside on another platform (GitHub) creates a layer of friction: having to sync, grant permissions, and wait for round-trips between two systems. Origin eliminates that layer by putting repos, PRs, and agents all in one place.

What bears watching next is how Cursor handles its relationship with GitHub. Currently, they have adopted a “friendly” posture — GitHub remains the primary source, while Cursor merely mirrors it. But this two-way sync could also serve as a stepping stone to help users become accustomed to hosting directly on Origin before ultimately leaving GitHub behind. That remains speculation rather than reality — but it is a trajectory worth watching.

For practical users, the immediate value comes down to one thing: agents and code are no longer separated by an intermediary platform. Whether this alone warrants switching is another question — Origin is in early beta, and abandoning a mature GitHub ecosystem for a brand-new platform without a track record is not a decision to rush into.