Cursor Origin: Git Hosting Built for AI Agents

Origin is a place to store, review and merge code, the same job GitHub and GitLab do. Cursor built it, and the pitch is aimed at teams whose code is increasingly written by agents rather than typed by hand. Cursor's tagline calls Origin a git forge for the agent era, with one line of reasoning underneath it: "Code is moving faster than any infrastructure was built to handle."

You cannot sign up for it yet. The page at cursor.com/origin is a waitlist and a promise, "We'll reach out when Origin is ready for you," with no product screenshots, no pricing and no published feature list. That gap matters for a guide like this, so the rest of this page is careful about which claims come from Cursor and which come from coverage of the demo.

The argument starts with a change Cursor already sells: agents that write code. Cursor's cloud agents run tasks on their own and open changes for review, and a team running several at once produces commits and branches faster than one person ever would. Hosting and review tools were designed around human pace, one engineer opening one pull request at a time.

Origin is Cursor's bet that the storage and review layer should be rebuilt for that faster pace instead of bolted onto tools made for it. Whether the bet pays off is an open question. The premise, that agent output is outgrowing GitHub-shaped workflows, is the same one behind Cursor's push into cloud agents, BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. and automated review.

Origin is not a from-scratch side project. Cursor signed a definitive agreement to acquire Graphite, a code-review startup, on December 19, 2025, and the Graphite founders now build Origin from inside Cursor. Graphite's calling card was stacked pull requests, a review style built for shipping many small, dependent changes quickly.

Tomas Reimers, one of Graphite's three co-founders, demoed Origin on stage at Compile. That lineage is the clearest signal of what Origin is actually about: review throughput, not just somewhere to push a repo.

Think of Cursor as assembling a stack that starts in the editor and ends at a merge. You write or direct code in Cursor, agents run tasks (locally or in the cloud), automated review runs on the result, and something hosts the repo and the pull requests. Origin is Cursor's answer for that last layer, the part GitHub holds for most teams today.

How tightly these layers connect inside Origin is mostly reported, not confirmed. BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. and Auto-review are real Cursor features you can use today on GitHub and GitLab. What Origin adds on top of them is the part to verify when it ships.

This is the part to read slowly, because most of the exciting detail about Origin has not been confirmed by Cursor. The product page is a waitlist. The architecture numbers and the feature list come from press coverage of the demo, and some figures that circulated were later traced to other products entirely.

Start with the why, then the mechanics. The guides below go deeper on the parts of Origin that have real precedent in Graphite and in Cursor's existing agent features, and they keep the same line between confirmed and reported.

• Agent-scale git explains the throughput problem Origin is built for, and why human-paced hosting strains under agents.
• Stacked diffs covers the review model Origin inherits from Graphite, with the gt workflow.
• Reviewing agent code is about reading diffs you didn't write, with BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. and Auto-review as the gates you have today.
• Parallel agents and merge conflicts is the practical safety guide for running several agents on one repo.
• Migrating from GitHub and code custody weigh what moving your hosting to an AI vendor actually means.