What Is Cursor Origin? Cursor’s New GitHub Alternative Explained

On August 17, 2026, Cursor shipped Origin — its own Git hosting and code-review platform — in early beta. It’s not another editor feature: Origin is a place to store, browse, review, and merge code, with Cursor’s coding agents wired in at the hosting layer rather than bolted onto the side. Two bits of context are worth naming and then setting aside. Origin launched the same day as a multi-hour GitHub outage, and it’s Cursor’s first major product since SpaceX completed its acquisition of Cursor’s parent, Anysphere, the week before. Neither is the story. The product is.

If you’re here you’re probably asking one of a few things: what is Cursor Origin, is it a GitHub replacement, what does it cost, and how do you get in. This walks through each from Cursor’s own docs and changelog, and is deliberate about separating what ships today from what Cursor says is still coming.

What Cursor Origin actually is

Origin is Cursor’s Git forge — “built for agent scale,” in Cursor’s framing. Underneath the positioning it’s a real Git host: you clone, push, and pull with standard git, you get repositories, pull requests, branch and repo settings, and a CLI, and you can browse and search code in the browser at cursor.com/codebase. The distinguishing idea is where the agent sits. An agent embedded at the hosting layer can act on a repository’s history and its open pull requests, not just whatever file happens to be open in your editor. That’s the whole bet: repos, pull requests, code browsing, and agents in one product surface instead of two.

What ships today

The confirmed early-access feature set is narrow but coherent. From Cursor’s docs and launch changelog, these work now:

• ◦Repositories — create Origin repos (including ones created by a Cursor agent), and clone, push, and pull with standard git.
• ◦GitHub mirroring — pull an existing GitHub repository into Origin so you can try the forge without moving off GitHub first.
• ◦Code browsing and search — read and search your team’s repos in the browser at cursor.com/codebase, in a new Codebase tab.
• ◦Pull requests — every repo has PRs with a timeline, commits, checks, and a files-changed diff; you review the diff, leave comments, and merge.
• ◦Origin CLI — terminal workflows for people who don’t want to live in the browser.
• ◦Integrations — Vercel (PR preview deploys), Depot (CI on GitHub Actions), and Buildkite (CI with Actions and native pipelines) are live on day one.
• ◦Agents — ask Cursor about the code you’re browsing and it can answer, make changes, update a PR, or push a branch; you can also connect Automations and cloud agents to Origin repos.

How the GitHub sync works

The mechanics are precise, and worth getting right. When you connect a GitHub repository, GitHub remains the source of truth and Origin stays synced with it: pushes keep going to GitHub for anything started there, and the Origin copy updates in real time to match. Pull-request interactions sync both directions — comment in Cursor and it posts to GitHub; react or reply on GitHub and it shows up in Cursor within seconds. CI reflects the same split: Depot and Buildkite run against repositories Origin hosts, while repositories mirrored from GitHub keep using whatever CI already runs on GitHub.

Migration, if you want it, is a deliberate act rather than a side effect. When a team decides Origin should be authoritative, it detaches the mirror: sync stops, the Origin copy becomes independent, and the original GitHub repository is left untouched. That detach is the actual one-way door; everything before it is a reversible trial of the workflow. In practice you can put Origin in front of a GitHub repo, use it for a week, and walk away having changed nothing.

Cursor Origin vs GitHub

The honest comparison is between a mature platform and an early-access essentials set with a different center of gravity. Here’s where they stand today:

Read plainly: Origin is not trying to reproduce all of GitHub today, and it doesn’t. GitHub’s advantages — Actions, Issues and Projects, the marketplace, the free tier, and the sheer gravity of the open-source network — are uncontested. Origin’s wager is the agent-native hosting layer, and for synced repos GitHub still holds the source of truth unless you detach. The accurate framing is a GitHub alternative aimed at agent-driven teams, in early access — not a drop-in replacement, and not a “GitHub killer.”

What Cursor says is still coming

Cursor is explicit that this is early. The launch changelog says agent-native features “ship soon” and that more app integrations are on the way. So the deepest part of the agent story is announced, not fully shipped — worth keeping in mind if you’re evaluating Origin specifically on how far the agents can go. Early coverage after launch reported an incremental step in that direction (agents subscribing to their own pull requests and working until checks pass), but treat the frontier of agent capability as a roadmap Cursor is filling in, not a finished surface.

Pricing: what Origin costs today

There is no separate price for Origin, and it’s worth saying that directly rather than guessing. In early access following its August 17 beta launch, Origin is bundled into Cursor’s existing paid subscriptions — code storage is available on eligible paid Cursor plans, not on free plans. Cursor has not published storage limits, and it has not committed to a post-beta price. The practical read: if you already pay for Cursor, Origin is included for now, but budget with the understanding that terms can change when it leaves beta.

How to access and get started

Access is rolling out in stages, so eligibility doesn’t guarantee immediate access. Once it reaches you, the path is short:

• ◦Be on an eligible paid Cursor plan — the paid individual and team plans. Free plans don’t get Origin, and admins can switch it off for their org.
• ◦Enable the beta and claim your namespace at cursor.com/codebase (Settings → Origin (Beta)). Choose carefully: during the beta you can’t change your namespace after it’s claimed.
• ◦If your team is on legacy privacy mode, switch to Privacy Mode first — Origin won’t enable until you do.
• ◦Create a new Origin repo, or mirror an existing GitHub repo to trial the workflow without leaving GitHub.
• ◦Browse and search at cursor.com/codebase, open a pull request, or point a Cursor agent at the repo.

Is Cursor Origin free?

No. Origin is available only on eligible paid Cursor plans — the paid individual and team plans — and not on free plans. Cursor hasn’t announced a separate charge for Origin; during early access it’s bundled into those subscriptions, with no published storage limits and no committed pricing for when it leaves beta. So it’s “included with a paid Cursor plan,” not free.

Is Cursor Origin a replacement for GitHub?

Not today. In early access Origin ships the essentials — repositories, pull requests, code browsing and search, a CLI, and GitHub repository mirroring — while GitHub still holds things Origin hasn’t built yet, like Issues, Projects, Actions, and a large integration marketplace. For synced repos GitHub also remains the source of truth unless you deliberately detach the mirror. Origin is better understood as an agent-native alternative you can trial alongside GitHub than as a drop-in replacement.

How do I move a GitHub repo to Cursor Origin?

You start by mirroring: point Origin at the GitHub repository and it syncs in both directions while GitHub stays authoritative. Nothing moves permanently until you choose to detach the mirror, at which point sync stops and the Origin copy becomes independent — and the original GitHub repository is left untouched either way. Until that step, it’s a reversible trial rather than a migration.