Cursor Origin: Git Hosting Built for AI Agents

Origin is a place to host code, review pull requests and merge them, the job GitHub and GitLab do today. The pitch is aimed at teams whose code increasingly comes from agents rather than from people typing. Its product page calls Origin a git forge for the agent era and gives one reason: "Code is moving faster than any infrastructure was built to handle."

You can use it now if your Cursor plan includes it. Origin began rolling out in early beta on August 17, 2026. Cursor's docs name the plans: Premium, Super, Ultra, Teams and Enterprise, plus the legacy Start, Pro, Pro+ and Ultra. Free and Plus are left out, even though the product page and the launch changelog say "all paid plans." Team admins can disable Origin from the dashboard.

The launch changelog called the first release "the essentials": repos, pull requests, code browsing and GitHub sync, with agent-native features to ship "soon." Today's docs also cover Code Tours, which walk a reviewer through each pull request, and stack commands in the Origin CLI. Cursor's release notes describe a merge queue as well.

Cursor still hasn't published a general-availability date, a separate price, a self-hosted option or an importer for GitHub issues. The status tracker keeps that list current.

The argument starts with a product Cursor already sells: agents that write code. Cursor's cloud agents run tasks on their own and open changes for review. A team running several at once produces commits and branches faster than one person does. Hosting and review tools were designed around human pace, where each engineer opens a pull request and waits for a teammate.

Origin is Cursor's bet that the storage and review layer should be rebuilt for that pace, not patched. Cursor's post on the Graphite deal names the same problem: as writing code got faster, reviewing changes, merging them safely and collaborating became the bottlenecks. Cursor's cloud agents and BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition. rest on the same premise. Whether the bet pays off is still an open question.

The case against deserves a fair hearing. Pull requests and review have absorbed a lot of change over the years. On Origin's launch-day thread, one commenter argued that LLM-generated code still fits normal pull requests and review. If that holds, the answer is better review tooling on the host you already have.

Your own queue shows which side you are on. If your open changes are waiting for a person rather than for infrastructure, a faster host won't shorten the wait. The throughput page walks through that diagnosis.

Cursor signed a definitive agreement to acquire Graphite, a code-review startup, on December 19, 2025. Graphite's signature feature is stacked pull requests, a review style built for shipping many small, dependent changes quickly. Cursor's announcement said "Graphite will continue to operate independently with the same team and product." Graphite's own post added that its whole team would join Cursor when the deal closed.

Neither announcement mentions Origin, and Cursor's Origin pages don't say who built it. Press coverage of Compile reports that Tomas Reimers, one of Graphite's three co-founders, demoed Origin on stage. The clearest overlap is in the product: Origin's CLI reference documents stacks, the review style Graphite built its business on.

The order in which things shipped matters for a trial. Coverage of the June demo dwelt on agent features for review and merge, such as automatic conflict resolution, but the August 17 release led with hosting: repos, sync, pull requests and apps. The settings docs still warn that the access and protection screens are being redesigned.

When your team gets access, spend the first hour on those controls. A trial depends on who can see and merge code more than on any review feature.

Cursor's products line up from the editor to the merge. You write or direct code in Cursor, agents run tasks locally or in the cloud, automated review checks the result, and a host stores the repo and its pull requests. Origin is Cursor's answer for that last layer, which GitHub and GitLab already serve.

Cursor documents how these layers connect to Origin. Cloud agents and Automations can clone, branch, push and open pull requests on Origin repos, and a local agent can create a repo with the Origin CLI. BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition. lists Origin as a supported host, next to GitHub, GitLab and others.

Cloud agents, Automations and BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition. all need a plan that includes them, and Free and Plus don't.

The layers don't fail in proportion to their height. Losing the editor for an afternoon is an inconvenience, but losing the host stops everything, so it is the layer to change last. Origin asks for that layer from an early beta that is still redesigning its access and branch-rule settings.

Read this part slowly, because the details that made the launch exciting and the details Cursor has shipped are different lists. Cursor's docs and release notes confirm the hosting and a growing set of review features. The throughput numbers and AI features from the June demo still come only from press coverage.

Each status means something specific. Confirmed means a Cursor page says it: the docs, the changelog or the product page. Release notes are first-party too, but a feature that appears only there has no docs page yet to check its settings against. Reported means an outlet described something shown on stage. Give that more weight than a rumor and much less than documentation.

The beta changes what to do with the demo claims. Keep discounting them, but don't ignore the beta itself. A team that waits for the agent-native features before it looks will end up judging a git host under time pressure. Planning a quarter around features Cursor hasn't documented loses the quarter. Name in advance the one signal that would change your plan, and use the status tracker to watch for it.

Start with the why, then the mechanics. The guides below go deeper on the parts of Origin with the most behind them, in Graphite's history or in Cursor features that already ship. They keep the same line between confirmed and reported.

Read them in this order. Diagnosis comes first, because if review isn't where your work piles up, none of the rest is urgent this quarter. The review model comes second, since stacks and review bots work on the host you have today. Custody comes last, and only if the first two came back positive, because it is the one decision on the list that is hard to reverse.

• Agent-scale git explains the throughput problem Origin is built for, and why human-paced hosting strains under agents.
• Stacked diffs covers stacked review: Graphite's gt workflow, GitHub's native stacks and Origin's stack commands.
• Reviewing agent code is about reading diffs you didn't write, with Agent Review and BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition. as the automated passes 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 means.

Team size changes how skeptical to be, not what to read. Four people can mirror a repo on a Saturday and detach it on Sunday. Four hundred can't, so the same early-beta docs earn a different answer from each.