Cursor Origin: What the New Code Hosting Platform Actually Is

Origin is Cursor’s git forge: a code hosting platform built for the speed agents operate at. Repositories, pull requests, browsing, GitHub sync, and the agent layer in one product. Early beta rolled out to paid plans in August 2026. If you only know Cursor as the editor, this is the bigger shift.

What Origin is

In plain terms, Origin lets you host Git repositories inside Cursor’s ecosystem.

You claim a codebase name (your team’s namespace), create or sync repos, push and pull with standard Git, open and merge pull requests, and browse code at cursor.com/codebase. There is an Origin CLI for terminal workflows, and agents can create repos or push branches as part of a task.

Cursor describes it as infrastructure “designed for agent scale.” That is the honest pitch. Agents create branches, touch many files, open PRs, and iterate. Owning the repo layer means Cursor can wire agents, reviews, checks, and deploy previews together without sending you to three tabs.

This is not a side feature. It is Cursor moving from “where you edit” to “where your team stores, reviews, and ships.”

What you get in early beta

According to Cursor’s docs and changelog, the first release focuses on essentials:

• Origin-hosted repos. Create a new repository from the Codebase tab, install the CLI, push a local project. Your code lives at URLs like cursor.com/codebase/{your-namespace}/{repo}.
• GitHub sync. Connect GitHub, pick orgs and repos, and mirror them into Origin. Synced repos update in real time. You can browse and pull from the Origin copy while pushes still go to GitHub, which stays the source of truth for repos that started there.
• Pull requests. Every repo gets PRs: timeline, commits, checks, files changed. Review diffs, comment, merge inside Cursor. On synced repos, PR activity syncs both ways between Cursor and GitHub.
• Browse and search. Code review and exploration in the browser without cloning everything locally first.
• Agents in context. Ask questions about code you are viewing. Agents can answer, edit, update PRs, or push branches from the same surface.
• App integrations. Vercel, Depot, and Buildkite connect from repo settings. Vercel can attach preview deploys to PRs; CI can run GitHub Actions workflows or native pipelines.

“Agent-native features ship soon” is Cursor’s own wording. Treat the current beta as forge plus sync plus review, with deeper agent workflows still arriving.

How this fits the Cursor story

I wrote about vibe coding tools and why instant site makers are a different category from real development. Origin sits firmly in the second camp. It assumes Git, PRs, and ownership. It does not replace engineering with a prompt-to-app dashboard.

It also extends the argument I previously wrote about in a blog post (AI as Your CMS). That post was about Git-native editing and deploy pipelines. Origin pushes the same idea one layer down: keep the repo central, but let the agent platform own more of the loop around it.

For agencies and product teams already on Cursor agents, the practical win is fewer context switches. Code, PRs, reviews, and agent runs share one namespace instead of IDE plus GitHub plus CI tabs.

Who can use it (and what to watch)

Origin is on Pro, Teams, and Enterprise paid plans. It is not on the free tier. Rollout is staged, so you may not see it immediately even on a paid account.

Setup starts at cursor.com/codebase: claim your codebase name, then create or sync repos. During beta, you cannot rename the namespace after claiming it, so choose carefully.

Enterprise admins can opt teams out. Teams on legacy privacy mode need to move to Privacy Mode before enabling Origin.

Pricing detail, long-term data handling, and migration paths beyond GitHub sync are still thin in public docs. That is normal for an early beta, but it means Origin is worth trying on a non-critical repo before you bet the whole company on it.

GitHub rival or GitHub companion?

For most teams today, Origin is a companion, not a replacement.

Synced repos keep GitHub as source of truth. Origin is where Cursor-native browsing, agent work, and in-product PR review happen on top of that copy. Origin-hosted repos (pushed directly to Cursor) are a different path: greenfield projects or experiments where you are fine living inside Cursor’s forge.

That split matters. If your compliance, billing, and audit trail live on GitHub today, sync mode is the low-risk entry. If you are starting a small product and already live in Cursor agents all week, hosting on Origin may be simpler than standing up another remote.

Either way, Cursor is no longer competing only with editors. It is competing for the repository layer too.

A simple decision rule

• Happy on GitHub, want agents closer to PRs? Sync repos into Origin and stay on GitHub as source of truth.
• Starting something new inside Cursor and want one stack? Try an Origin-hosted repo and wire Vercel or CI from the Apps tab.
• Need enterprise guarantees today? Read admin controls, privacy mode requirements, and opt-out policies before you migrate anything important.

Origin does not change my default advice for client sites: you still want a repo you own, review before merge, and hosting that stays boring. It does change where that repo might live if Cursor becomes the hub your team already works in.

If you want help mapping Origin, GitHub, and a static deploy pipeline for a real project, get in touch.