What Is Cursor Origin? A Beta Git Forge, What It Lacks, and the GitHub Coexistence Tradeoff
What Cursor's git forge shipped in beta, what it lacks, and how GitHub coexistence actually works before you claim a namespace.
One-line job: Decide whether Cursor’s new git forge fits your team now, and know exactly what it does and doesn’t replace before you claim a namespace. Audience: Devs and team leads evaluating hosting for agent-heavy workflows. Not for: Anyone looking for a free code host or public-repo hosting. Origin has neither. Last verified: 2026-08-24 Evidence weight: documentation-verified
Cursor Origin is in early beta, launched August 17, 2026. Everything below reflects beta reality: features change without notice and there is no GA date.
Cursor Origin is a git forge: code hosting, pull requests, and browser-based code browsing/search built by Cursor (Anysphere). The official line is “a git forge for the agentic era,” and the pitch is infrastructure designed for the volume of code AI agents produce. It launched into early beta on August 17, 2026, rolling out in stages to paid plans (cursor.com/origin).
It was built by the Graphite team, the stacked-diff code-review company Cursor acquired on December 19, 2025. Graphite co-founder Tomas Reimers demoed it at Cursor’s Compile event on June 16, 2026 and led the launch discussion on Hacker News.
What actually shipped
The beta covers the core hosting loop:
- Create Origin repositories through the web UI, the CLI, or by asking a Cursor agent
- Clone, push, and pull with standard git against
https://origin.cursor.com/{owner}/{repo}.git - Sync (mirror) existing GitHub repositories: history, branches, tags, and two-way PR sync
- Pull requests with review tabs (Activity / Commits / Checks / Files Changed), line comments, reviews, merging, and pre-merge conflict surfacing
- Code browsing and search at cursor.com/codebase
- Repo settings: General, Permissions, Rules and Protections, Apps
- Third-party CI/deploy apps: Vercel, Depot, and Buildkite
- The Origin CLI (
origin) for terminal workflows - Automations and cloud agents can work against Origin repos
What has NOT shipped
Just as important, per the docs:
- Issues: none native. For mirrored repos they stay on GitHub.
- First-party CI: no Actions equivalent. Only the three named apps above.
- Agent-native features: promised “soon” in the changelog (intent-aware conflict resolution, a merge queue, native stacked diffs from the June demo). Treat these as unpublished; nothing ships until it’s documented.
- Self-hosting, a GA date, standalone pricing, public repos, a free tier: all absent.
Access and pricing
Origin is available on Pro, Teams, and Enterprise paid plans only. During the beta it’s included in existing subscriptions with no separate price published (cursor.com/docs/origin). Two access caveats: teams on legacy privacy mode must switch to Privacy Mode before enabling Origin, and Enterprise admins can disable it org-wide at any time.
The namespace decision you can’t undo
Before anyone uses Origin, somebody claims a codebase name. That name becomes the {owner} part of every repo URL (cursor.com/codebase/{owner}/{repo}). During the beta it cannot be changed after claiming, not by you, not by an admin, not by support (cursor.com/docs/origin). Any team member can claim it, so coordinate before someone grabs a typo.
How GitHub coexistence works
This is the part most likely to be misreported, so it plainly: Origin is not a GitHub replacement today. Repos can be synced from GitHub with GitHub remaining the source of truth; PRs sync in both directions; you can detach later. DigitalOcean’s comparison reached the same verdict: most teams run Origin alongside GitHub, which “adds a layer rather than replacing GitHub’s role.”
What does not come over when you mirror: GitHub Issues, GitHub Actions workflows, and branch protection rules. CI has to be rebuilt using Origin’s app integrations.
What “coexistence” means day to day
The mirror model has practical consequences worth spelling out. Your team keeps working in GitHub as before: issues filed there, Actions running there, branch protections enforced there. Origin receives a continuously-updating copy plus two-way PR sync, so a reviewer can work in either surface. That’s genuinely useful when a reviewer lives inside Cursor all day and wants diffs beside their agent sessions. It also means Origin inherits nothing authoritative: if GitHub is source of truth, Origin is a view with review powers, not the system of record. Teams should decide explicitly which surface merges win in, because two-way sync with an unclear merge authority is how histories diverge.
Privacy model
Repos follow the Privacy Mode of the namespace owner (the team or individual who owns the repo). Legacy privacy mode is excluded entirely. If your org’s data-handling requirements are strict, verify this mapping against your own compliance needs before syncing anything sensitive.
Company context, stated as fact
Anysphere was acquired by SpaceX in a $60B all-stock deal (SEC 8-K filed June 16, 2026); Cursor announced the acquisition’s completion on August 14, 2026, three days before the Origin beta opened. That’s context, not commentary. Separately, Origin launched the same day GitHub suffered a multi-hour global outage, which shaped early press coverage (“Cursor capitalizes on GitHub frustration” per TechCrunch). The timing was coincidence as far as any reporting shows.
One number-circulation warning: Compile-demo figures such as “thousands of parallel agents” and “~22.6 commits/sec” circulated via press coverage, not Cursor documentation, and third-party trackers traced some numbers to other systems. We omit them as unverifiable.
The agent-volume context
Why build a forge at all? Because of volume. GitHub’s own Octoverse 2025 report counted 43.2 million pull requests merged per month, up 23% year over year, and GitHub’s CTO wrote publicly that GitHub needs to design for 30 times its scale. LeadDev and IncidentHub counted 257 separate GitHub incidents between May 2025 and April 2026. Whether or not you accept Cursor’s framing, the underlying pressure is real: agents generate far more commits, branches, and PRs per developer than the workflows most forges were designed around.
That pressure is also why skepticism matters. A forge built quickly around one vendor’s agents could optimize for demos rather than durability. The HN thread’s API-compatibility questions (will Origin ever emulate the GitHub API so existing tooling works unchanged?) went unanswered at launch. If your tooling depends on GitHub-specific integrations, that gap is decisive today.
Reception so far
The launch HN thread (596 points, 453 comments) mixed curiosity with skepticism: “basically nothing new here” was a common take, with unanswered questions about API compatibility and CI workflows. Reimers wrote: “Expect a lot more from us… over the next few weeks you can expect a handful of features starting to change source control to better understand and work with agents.” A week in, the fairest read is: real product, real gaps, unproven trajectory.
How it compares
Against GitHub: GitHub has 18 years of maturity, a free tier, public repos, first-party Actions, issues, and a marketplace. Every one of those is something Origin lacks today. Origin’s claimed edges are agent-native design, fewer context switches between editor, host, and review, fresh scalability headroom, and Graphite’s stacked-diff review DNA.
In the wider category it sits alongside Zide, the agentic desktop with forge features that we covered separately, GitLab and Bitbucket, and self-hosted options like Gitea and Forgejo.
Should you look at it?
If your team already pays for Cursor Pro or above and runs heavy agent workflows, trying Origin on a non-critical mirrored repo costs nothing extra. If you need issues, first-party CI, public repos, or contractual stability, none of those exist here yet. And whatever you do, think hard about that namespace name before claiming it.
Done means
You can state what Origin shipped versus hasn’t, which plans include it, how mirroring treats GitHub as source of truth, why the namespace claim is permanent, and whether its privacy model fits your team, each point traceable to cursor.com docs or the cited independent coverage.
What this article does NOT cover
- Step-by-step setup: see How to Install, Set Up, and Use Cursor Origin.
- Pricing details: none published beyond plan-gate inclusion during beta.
- Performance benchmarks: no verified third-party numbers exist.
Related guides
- Different ways of using LLMs for coding: eight patterns
- AI coding is a nightmare, not the only one
- Agents and the deploy gate: when they push
- Start here: local AI and agents
Sources
Primary:
- cursor.com/origin
- docs: origin overview
- docs: origin CLI
- docs: create repository
- docs: mirror GitHub
- docs: pull requests
Independent:
Sources
Submit a take
Have a different read on this? Drop a comment below — your email isn't published, and I read every one. Nothing leaves the site until I approve it.