Cursor Origin: What to Do About It in 10 Minutes

Sync two GitHub repos into Origin and review one PR there. Ten minutes. That answers whether it's worth more.

Cursor shipped Origin on August 17, 2026. It's a git forge inside the editor: repos, pull requests, review, merge. Early beta, included in every paid Cursor plan at no extra cost. Free plans don't get it.

Do this first

1. Open the Codebase tab in Cursor. No tab means the phased rollout hasn't reached you.
2. Claim your codebase name at cursor.com/codebase. Read the warning below before you type it.
3. Connect your GitHub org and pick two repos to sync.
4. Review one open PR in Cursor instead of github.com.

Steps 1 to 3 take about 5 minutes. Step 4 is the actual test.

The one step you cannot undo

Your codebase name becomes the {owner} in every repo URL: cursor.com/codebase/{name}.

It can't be renamed or transferred. Ever. Pick the name you'd want on a company handle, not test-2.

Two blockers to clear first:

• Origin uses the Privacy Mode of whoever owns the namespace, the team or the individual.
• Teams on legacy privacy mode have to switch to standard Privacy Mode or Origin won't turn on.

Read next: Every Major AI Coding Tool Now Has a No-Approval Mode

Recommended

Recommended

Every Major AI Coding Tool Now Has a No-Approval Mode

You ask your coding agent to scaffold a project. It creates files, installs packages, runs setup commands, and starts fixing import errors. Somewhere around the eighth "Continue" click, you stop reading what it's asking.…

Read next

What you get

1. Repos: create in the Codebase tab, then clone and push with ordinary git via the Origin CLI.
2. Pull requests: timeline, commits, status checks, file diffs, review and merge in the editor.
3. GitHub sync: mirror selected repos in real time. GitHub stays the source of truth. PR comments sync both ways in seconds.
4. Agents: read code and PRs, push branches, update PRs, locally or in a cloud sandbox that runs with your laptop closed.
5. CI and deploys: Vercel preview per PR. Depot and Buildkite run your existing GitHub Actions.

What's missing

1. No issues, projects, or discussions.
2. No native CI of its own.
3. No open source or public repo story.
4. Agent-native features, the whole point, are "shipping soon."

Number 4 decides whether Origin matters. Matching GitHub's 2015 feature set is no reason to move. A forge where agents open, review, and land PRs faster than humans can read them is a different product, and that's the target.

Context, if you want it

Origin started rolling out Monday. GitHub degraded globally about three and a half hours later. A Cursor team member's line: "We were going to ship this earlier, but GitHub was down." The New Stack quoted the sharper read: "If GitHub was stable, these alternatives would not be as interesting."

The PR review quality isn't an accident. Cursor bought code review startup Graphite in early 2026; co-founder Tomas Reimers works on Origin and answered developers on Hacker News all launch day.

Hacker News split on trust. Handing a codebase to an AI vendor is a bigger ask than handing it a context window, and paid plans were enrolled opt-out rather than opt-in. If "who holds this code and under what terms" has to pass a security review at your company, read the terms before step 2.

Where this leaves you

Syncing repos costs a paying Cursor customer nothing and is reversible. Claiming the namespace is not reversible. Moving a production codebase to Origin as the source of truth is not something this beta has earned.

Next: open the Codebase tab and check whether Origin is live on your account.

Sources: Cursor changelog, Cursor Origin docs, The New Stack, SiliconANGLE, TestingCatalog, VentureBeat