Cursor launches Origin, a git host built for agents, and keeps GitHub as the backstop
Cursor's Origin puts repositories, pull requests, and its coding agents on one surface, backed by an S3-based git store built for agent-scale churn. It syncs with GitHub rather than replacing it, so the switching cost stays low for now.
Cursor has launched Origin, a code hosting platform that puts repositories, pull requests, and the editor’s AI agents on the same surface. It arrived in early beta on August 17 for paid users, on a day GitHub was in the middle of a multi-hour outage, and the timing did a lot of the marketing. The more durable question is not whether developers are annoyed with GitHub this week, but what changes when the company that makes your AI coding agent also hosts your code.
What Origin actually is
At launch, Origin is a working code forge rather than a preview. From a new Codebase tab in the Cursor editor, or from the command line, developers can create native repositories, run standard git clone, fetch, push, and pull, browse and search code in the browser, and open pull requests with comments, reviews, checks, conflict handling, and merges. It ships with branch protections, repository settings, and a public REST API. Cursor’s framing is that “your code, PRs, and agents are now in the same place,” and the practical version of that is concrete: a developer can hand an agent a review comment and have it revise the pull request in the same window where the code was written, without bouncing between an editor and a separate hosting site.
Built for agent-scale churn
The more novel part sits underneath. In a companion engineering post, Cursor describes Origin’s storage layer, Continuity, which records every push to S3-compatible object storage before acknowledging it, keeps all pushes linearizable (applied in a single consistent order), and scales to roughly 100 replicas for read-heavy repositories. Cursor cites throughput of up to 120 pushes per second on standard S3 and more than 300 on its faster express tier.
The reason for that design is the thesis behind the whole product. Coding agents, Cursor argues, do not behave like human teams working in one large repository. They spin up “vast numbers of small, often throwaway repositories,” and Continuity is tuned to scale in both directions at once: enormous monorepos spread across many replicas, and swarms of tiny, short-lived repos. For a working developer that mostly stays invisible, but it is the part of Origin that a general-purpose forge is not built to do, and it is where Cursor is betting the real difference lies.
GitHub stays the source of truth
Cursor is not asking anyone to migrate. Origin is designed to run alongside GitHub: connect an account, pick an organization, and sync repositories, while pushes keep going to GitHub, which stays “the source of truth for anything started there.” Comments made in Cursor post back to GitHub within seconds, GitHub activity shows up in Origin, and a synced repo can be disconnected at any time. The launch also arrives with an ecosystem attached. Vercel spins up a preview deployment for every pull request and ships to production on merge, while Depot and Buildkite run existing GitHub Actions workflows without modification. Positioning Origin as a low-risk layer on top of GitHub keeps the switching cost near zero, and it buys Cursor room to build an AI-native workflow around existing repositories before asking developers to make a more consequential move.
The trade to weigh
The convenience is real, and so is the concentration. Consolidating the editor, the agent, and the code host with a single vendor removes friction, and it also puts your source, your review process, and the models that rewrite your code in one place, now owned by SpaceX after its acquisition of Cursor this summer. None of that is a reason to avoid Origin, but it is the question a team should ask before leaning in: what are the data terms, how portable is the history, and how clean is the exit. Because Origin syncs with GitHub and repos can be disconnected, the lock-in is soft today. The signal to watch is whether it stays soft as agent-native features accumulate on Origin and not on the GitHub copy.
What to watch
The near-term tests are whether Origin’s agent features stay additive to GitHub or begin to diverge in ways that make the sync lossy, what pricing looks like once it leaves beta, and whether any other AI-editor vendor follows Cursor into hosting rather than integrating with the forge that already exists. The forge has effectively been GitHub’s for a decade. The pitch here is that agents change what a forge is for, and that is a claim worth watching prove itself outside an outage-day launch. Stackmaven will revisit on or around November 18.