Cursor Origin.

Origin is Cursor's git forge — a place to host repositories, review pull requests, and collaborate on code, in the same product family as the editor and its agents. Cursor announced it on stage at the Compile conference in June 2026 with a one-line pitch: a git forge for the agentic era. On 17 August 2026 it started rolling out in early beta to paid plans.

Concretely, Origin gives you a new Codebase tab at cursor.com/codebase: create repositories there (or have a Cursor agent create one), clone, push, and pull with plain git, mirror existing GitHub repositories with live sync, browse and search your code on the web, and open, review, and merge pull requests.

The team behind it matters. Origin is led by the people from Graphite — the stacked-diff code review company Cursor acquired — which tells you where this is heading: not just storage, but a review and merge workflow rebuilt around the volume of changes agents produce.

GitHub was designed around a human assumption: one developer, a handful of branches, a few pull requests a day. Agents break that maths. A single developer running parallel cloud agents can generate dozens of branches and PRs in an afternoon — each needing review, checks, and a merge. The forge becomes the bottleneck.

Cursor's answer is to put the code, the PRs, and the agents in the same place. On Origin, an agent isn't a bot account bolted onto your repo — it's a first-class citizen. From a repository page you can ask an agent questions about the code, have it make a change, update an open pull request, or push a branch. Automations run cloud agents on a schedule or when source-control events fire — a push to main, a PR opened.

The bet is the same one Cursor made with the editor: when the workflow is agent-shaped, a tool designed for that shape beats a general-purpose one with agents retrofitted.

• A paid Cursor plan— Origin is available on Pro, Teams, and Enterprise. It's not available on free plans, and access opens in stages during the early beta, so it may not appear in your account on day one.
• A claimed codebase name — someone on your team claims a namespace at cursor.com/codebase first. Every repository then lives at cursor.com/codebase/{owner}/{repo}.
• Current Privacy Mode— Origin follows the namespace owner's privacy settings, and teams still on legacy privacy mode can't enable it until they switch to the current Privacy Mode.
• Admin sign-off, if you're Enterprise — enterprise organisations are excluded by default and opt in via admin settings.

From cursor.com/codebase, select New, give the repository a name, and choose its visibility — Internal (anyone on your team) or Private (only people you grant). Then copy the clone URL from the green Code button and push from your machine:

That's the whole trick: Origin is git-compatible, so nothing about your local workflow changes. The remote URL format is https://origin.cursor.com/{owner}/{repo}.git and every git command you already know — clone, fetch, pull, push, branch — works as-is.

You can also skip the UI entirely: ask a Cursor agent to create the repository. An agent can install the Origin CLI, authenticate as you, create the repo, wire up the remote, and push the first commits — one prompt, zero clicking.

The CLI is the piece that makes plain git "just work". One command installs it, and origin auth login signs you in through the browser and configures a git credential helper — after that, push and pull against Origin remotes need no tokens, no SSH keys, no further setup.

Two small things worth knowing: if your shell can't find origin after installing, add ~/.local/bin to your PATH; and origin update keeps the CLI current as the beta moves quickly.

Nobody moves a production codebase to a week-old forge, and Cursor knows it. That's why the most important Origin feature for most teams is mirroring: connect the Cursor GitHub app, pick a repository at cursor.com/codebase (you'll need admin access to it on GitHub), and Origin keeps a live copy — history, branches, and tags — that updates as the GitHub repo changes.

Crucially, GitHub stays the source of truth while mirrored, and pull requests sync both ways: a PR opened on Origin appears on GitHub, and you can review GitHub PRs from Origin as if they were native. What doesn't sync: GitHub Issues, and your CI/CD workflows and secrets. If the evaluation goes well, Detach from GitHub flips the mirror into a standalone Origin repository; if not, you delete the mirror and GitHub never noticed.

Pull requests on Origin will feel familiar: push a branch, open a PR against the base branch, request reviewers, comment on lines, and merge when checks pass. Each PR has four tabs — Activity (every open, comment, review, and status change in order), Commits, Checks, and Files changed — and Origin flags merge conflicts before you hit the button.

The agent layer is where it stops feeling like GitHub. From a repository, agents can answer questions about the code, make changes, update open PRs, and push branches. Automations — set up at cursor.com/automations or from the Agents window — run cloud agents when a branch is pushed or a PR is opened: think a standing reviewer on every PR, a changelog writer on every merge to main, a triage agent on every failing check.

Given the Graphite pedigree, expect the review workflow to be the fastest-moving part of Origin — stacked-diff-style review and merge automation are the obvious next chapters, though the early beta docs don't promise them yet.

Once a repository is on Origin, a small ecosystem is already waiting:

• Vercel — preview deployments for your branches and PRs, connected from repository settings.
• Buildkite and Depot — CI/CD that can run your existing GitHub Actions workflows, so a mirrored repo doesn't lose its pipeline.
• Browse and search — the Code tab renders the tree, press T to jump to a file, and the header search finds files and code matches across the repository.
• Repository controls — settings cover general options, permissions, rules and protections, and connected apps, with codebase-level settings for the team namespace.

Know the edges too: no issues, no native CI, no public open-source hosting story yet, and the roadmap items that got the launch-day attention — stacked PRs, merge queues, AI-assisted conflict resolution — are still ahead of the shipping product. Origin today is a fast, git-compatible forge with agents built in; the agentic-era ambitions arrive in instalments.