Cursor spent two years being the place you write code. On 17 August it became a place you can keep it.
Origin is code hosting: repositories, pull requests, browsing, and bidirectional sync with GitHub. It is in early beta on all paid plans, excluding enterprise organisations whose administrators opt out. Cursor's own framing is the giveaway — your code, PRs and agents are now in the same place.
What shipped
This is a fuller first release than "code hosting" usually implies:
- Origin Repos — a new Codebase tab for creating and managing hosted repositories, with customisable URLs
- GitHub sync — existing GitHub repos sit alongside Cursor-hosted ones, with real-time bidirectional updates
- Pull requests — timelines, commits, diffs, comments and merging, not just a viewer
- Repository settings — access controls, sync status monitoring and app connection management
- Apps — Vercel for preview deployments, plus Depot and Buildkite for CI
The sync is the strategy
Bidirectional GitHub sync is what makes this adoptable, and it is worth understanding why that matters more than any individual feature.
A code host that demands migration asks for a decision nobody makes casually — you are moving your history, your integrations, your CI and your team's habits at once. A code host that syncs asks for nothing. You try it on one repository, your GitHub remote keeps working, and nothing breaks if you stop.
That is how platform shifts actually happen: not by convincing anyone to switch, but by being present alongside the incumbent until switching is a formality. The risk sits entirely on the other side of that trade — a low-friction entry usually means a gradual, unexamined accumulation of dependency.
Why an agent company wants your repository
The obvious read is competition with GitHub. The more useful read is that agents work better when the code, the review and the execution live in one system.
An agent that has to authenticate to a separate host, poll for pull request state and reconcile two sources of truth is doing work that adds no value. Cursor's cloud agents got three times faster to first token on 13 August by pre-baking environments; owning the repository removes another category of latency and another integration that can break.
That logic is sound. It is also the logic behind every vertically integrated platform, and it produces the same trade every time: things work better together, and you can take fewer of them elsewhere.
Early beta means early beta
The status matters. Early beta on a code host is a different proposition from early beta on a chat feature — this is where your source lives.
Enterprise organisations can have administrators opt out, which is the right control to have and worth exercising deliberately rather than by inaction if your organisation has a position on where code may be stored.
A sensible way in: sync a repository rather than creating one, keep GitHub as the authority, and treat Origin as a second view of the truth rather than the truth. Then check what would be lost — issues, actions, integrations, history of reviews — if you did ever make it primary.
The timing is remarkable
Cursor announced code hosting on the same day GitHub had a seven-hour incident affecting Git operations, the API, Actions, Issues, Pull Requests and Copilot authentication.
That is a coincidence rather than a plan — an outage is not something a competitor schedules around. But it is the kind of coincidence that gets remembered, and for some teams it will be the day both halves of a single question arrived at once: how much of our development stack depends on one company?