Cursor launches Origin, a GitHub rival for agents
The AI coding tool that just sold for sixty billion dollars is done borrowing someone else's git host.
Cursor began rolling out Origin today — its own code-hosting service — in early beta on every paid plan, with repos, pull requests, code browsing, and live GitHub sync in the first cut. Agent-native features, the company says, ship soon. Origin lives in a new Codebase tab inside the editor. Create a repo, push, and the code is hosted on Cursor. Existing GitHub projects can sit alongside: connect an org, pick what syncs, and Origin mirrors it in real time while GitHub stays the source of truth for anything that started there. Pull requests on those synced repos go both ways — comment in Cursor and it posts to GitHub; reply on GitHub and it shows up in Cursor within seconds.
That is the product. The argument underneath it is older. Cursor first pitched Origin in June at its San Francisco developer event as a "git forge for the agentic era," and the complaint is fair even if the branding is not subtle. GitHub and GitLab were built for people who write a patch, open a pull request, and wait. Agents do not wait. In the June demo, Cursor showed a swarm of agents pushing 22.6 commits per second on a single repository, sustaining 81,000 pushes and 295,000 clones an hour. A host designed around human review cadence is the wrong shape for that load. Origin's bet is that the editor, the agents, and the repo should be one surface: ask a question about the code you are browsing, and Cursor can answer, edit, update the PR, or push a branch without a tab switch.
The integrations are the tell that this is meant to replace a workflow, not decorate one. Vercel, Depot, and Buildkite are already wired in. Connect Vercel and every pull request gets a preview deploy; merge, and it ships. Depot and Buildkite run existing GitHub Actions workflows, so a team can move the host without rewriting CI on day one. Enterprise orgs can opt out. Everyone else on a paid plan can name a codebase and create a first repo today.
The timing is almost rude. GitHub spent August 17 fighting another outage — core APIs and web pages down, a reported 50 percent failure rate on raw file serving that broke package installs and Docker builds. Notebookcheck notes, correctly, that launches like this are staged weeks ahead; Origin was not a panic ship. It did not have to be. Microsoft-owned GitHub has had a rough year of incidents, and a newly SpaceX-owned Cursor does not need a conspiracy to notice. We covered the close of that deal earlier this month — SpaceX completes record $60B Cursor acquisition. Owning the editor was the first lock-in. Hosting the code is the second.
Why it matters: the coding-agent war is no longer about which model writes the nicest diff. It is about who owns the loop those diffs travel through — review, CI, preview, merge. GitHub still has the network, the Actions graph, and a decade of enterprise contracts. Origin is a beta that still treats GitHub as the source of truth for anything imported. That is the polite phase. The impolite phase is when agents prefer the host that does not make them wait, and the repos follow.
What to watch: whether Origin-native repos — the ones that never touch GitHub — start showing up in serious team workflows, or whether this stays a sync layer with nicer furniture.
Would you move a real repo off GitHub for an agent-native host, or is the network effect still the whole product? Tell us in the comments.
