Cursor Launches Origin Code Hosting to Take on GitHub

The biggest change in code hosting this month is not coming from GitHub. Cursor, fresh off its $60 billion acquisition by SpaceX, is rolling out Origin, its own code hosting service, in early beta to all paid plan users starting this week. The pitch is simple: your repositories, pull requests, review comments, and AI agents finally live in the same place you already code.

What Origin Actually Is

Origin is a hosted Git service that lives inside Cursor, announced in the Cursor changelog on August 17. It begins rolling out in early beta on all paid plans, with the exception of enterprise orgs whose admins need to enable it first. The company says it is starting with the essentials: create a repository, push code, open pull requests, review diffs, and manage access, all without leaving the editor.

The new Codebase tab is where Origin repos live. Clicking +New creates a repository, and the name you pick becomes part of every repo URL under cursor.com. The CLI setup is handled from a page inside the editor, so the friction of moving between terminal and browser disappears.

The GitHub Sync Story Is the Interesting Part

Origin is not asking you to abandon GitHub, at least not yet. Your existing GitHub repos can sit alongside the ones Cursor hosts. Connect GitHub to Cursor, pick an organization, and the repos appear in Origin as synced copies that update in real time. You can browse, search, and pull from the copy inside Origin while pushes keep going to GitHub as usual.

Pull requests on synced repos work both ways: comment in Cursor and it posts to GitHub, react or reply on GitHub and it shows up in Cursor. For teams that live in Cursor all day, that removes the context switch that normally comes with reviewing PRs in a browser tab.

The endgame is visible in the phrasing: “Your code, PRs, and agents are now in the same place.” Origin is not competing with GitHub on repository features. It is competing on the workflow argument that code review is an AI problem now, and AI agents should be able to see, comment on, and eventually drive the whole pipeline.

The AI Angle

This is where Origin diverges from every code hosting service before it. Because repos live inside Cursor, you can ask Cursor questions about code you are browsing and get answers grounded in the actual repository, not a synced snapshot. The app ecosystem is next: Cursor is building integrations so the whole stack works with Origin, and the first visible one is Vercel, where every pull request gets a preview deployment you can test and comment on directly from the PR view.

The broader trajectory is clear even in beta: Cursor has spent 2026 moving from autocomplete to agents to, now, the repository layer underneath both. Owning code hosting means owning the data, the review process, and the deployment hooks, which is exactly the surface area where AI coding agents are becoming the primary interface. If agents review most PRs in a few years, the hosting provider that controls the agent’s access to code owns the loop.

The acquisition context matters here. Cursor is now part of SpaceX, with access to what it calls the largest GPU fleet in the world, and the Origin launch is the first major product move since the deal closed on August 14. That compute advantage applies to hosting economics too: serving preview environments and repository indexing for millions of repos is cheaper when you run your own infrastructure at scale.

The Honest Caveats

Origin is early beta with “the essentials,” which means the features developers take for granted from GitHub, such as advanced branch protection, required reviews, secret scanning, and a mature third-party app marketplace, are not all here yet. Teams with compliance requirements will stay on GitHub for now.

The GitHub sync relationship is also a one-way door in disguise. Synced repos update in real time, but if Origin grows into the primary workflow, the switching cost back to GitHub-only hosting rises. Developers who value portability should keep an eye on whether Cursor allows clean migration out, because the same lock-in logic that GitHub has been accused of for years can apply to an AI-native host.

There is also the question of what “free” code hosting economics mean for a service that now has a $60 billion parent with data center ambitions. Origin is included in paid plans today; pricing for storage, bandwidth, and preview minutes at scale has not been announced. History suggests the free tier of hosted Git gets generous, then monetized, and the monetization point is worth watching.

Who Should Care

Cursor Pro and Ultra users who live in the editor get the most immediate value: PR review inside the app, two-way GitHub sync, and agents that can see the whole repository. Individual developers with small projects can plausibly move everything to Origin today. Teams evaluating whether to leave GitHub should wait for the beta to mature and for the missing enterprise features to land. Competitor-watchers should note that the AI coding market is now converging on a full stack: model, editor, and repository, and the race among Cursor, GitHub Copilot, and the rest just widened. Our Cursor acquisition coverage lays out the SpaceX deal behind this move, and the OpenAI Codex guide covers the main independent alternative if you want a second tool in the loop.

The Bottom Line

Origin is a strategic bet disguised as a feature launch. Cursor is using its position as the most popular AI editor to reach up the stack into code hosting, where it can tie the agent experience to the repository layer and take on GitHub on workflow rather than feature parity. The beta is genuinely useful today for Cursor users, the GitHub sync is well designed, and the two-way PR flow is a real convenience. But the long game is data and agent access, and that is a fight GitHub is not going to cede quietly. For now, Origin is worth trying, worth watching, and not yet worth migrating your enterprise to.

Leave a Comment