Cursor Origin Code Hosting Review: Should Your Team Move Repos from GitHub?
On August 17, 2026, Cursor stopped being just an AI editor. With the launch of Origin, it now hosts your code: repositories, pull requests, code browsing, and GitHub sync live in the same place as the agents that write and review your changes. It is the first time an AI-editor company has stepped directly onto GitHub's home turf, and the launch thread spent days near the top of Hacker News. But the question that matters for developers and small teams is not "will Cursor replace GitHub?" It is narrower and more practical: should anything you own move today? This review looks at what Origin actually does in early beta, how the GitHub sync really behaves, where the gaps are, and which projects are safe to move now.Quick Verdict
| Question | Answer |
|---|---|
| What is it? | Cursor's own git forge: hosted repos, pull requests, code browsing, and real-time GitHub sync, with AI agents built into every repo |
| Best for | Developers already paying for Cursor who want agents, code, and PRs on one surface |
| Biggest strength | Agents in every repo â ask questions about code you're browsing, have changes made, PRs updated, branches pushed |
| Biggest caveat | Early beta: no Issues or project management, limited governance, and agent-native features still marked "shipping soon" |
| Access | Pro, Teams, and Enterprise plans only; not available on free plans, and access rolls out in stages |
What Origin Actually Is
Per the official changelog and the Origin docs, the early beta covers the essentials of a code host:- Origin repos. Create a repo from the new Codebase tab (or from a Cursor agent), then clone, push, and pull with standard git. An Origin CLI covers terminal workflows.
- Pull requests. Timeline, commits, checks, and files changed; review the diff, comment, and merge without leaving Cursor.
- Code browsing and search at cursor.com/codebase, for both Origin-hosted and GitHub-synced repos.
- Agents in every repo. Because code, PRs, and agents share one surface, you can ask questions about what you're browsing and have the agent make changes, update PRs, or push a branch.
- App extensions. Vercel integration gives every PR a preview deployment; Depot and Buildkite run your existing GitHub Actions workflows for CI, and Buildkite also runs its native pipelines.
{owner} in cursor.com/codebase/{owner}/{repo}. Two details matter here: during the beta you cannot change the namespace after claiming it, and any team member can claim it. Decide the name internally before someone grabs it on a whim.
How the GitHub Sync Actually Works
The sync is the most useful feature in this beta, because it lets you try Origin without moving anything:- GitHub stays the source of truth. For repos that started on GitHub, pushes keep going to GitHub. Origin holds a real-time mirror you can browse, search, and pull from.
- You choose what syncs, and can disconnect anytime. Access follows GitHub permissions â anyone with read or write access to a synced repo can view it in Cursor.
- PRs sync both ways. Comment in Cursor and it posts to GitHub; replies on GitHub show up in Cursor within seconds. Got a review assigned on GitHub? You can review and merge it from Cursor.
Origin vs GitHub, August 2026
| Dimension | Cursor Origin (early beta) | GitHub |
|---|---|---|
| Core hosting | Git repos with browsing and search | Mature, planet-scale hosting |
| Pull requests | Yes, with two-way GitHub sync | The ecosystem standard |
| CI/CD | Via Depot and Buildkite, running your existing GitHub Actions workflows | GitHub Actions, native and complete |
| Issues & project management | Not yet in early beta | Issues, Projects, Discussions |
| AI agents | Built into every repo: explain, edit, update PRs, push branches | Requires Copilot or external tools |
| Preview deployments | Vercel app integration per PR | DIY via integrations |
| Permissions & governance | Follows Cursor team settings and GitHub sync permissions; limited during beta | Mature org roles, branch protection, audit logs |
| Cost of entry | Requires a paid Cursor plan (Pro/Teams/Enterprise) | Free tier covers public and private repos |
Who Should Use It Now
- New side projects and experiments. No history to migrate, nothing to break â the cleanest way to try native hosting.
- Agent-heavy development. If Cursor's agents already do a large share of your coding, having code, PRs, and agents on one surface removes real context-switching cost.
- Existing paid Cursor users. Sync mode costs you nothing and risks nothing; it is a free look at the workflow.
Risks and Open Questions
- Beta churn. Early beta means UI and behavior can change, and the marquee agent-native features are announced but not shipped yet.
- Namespace lock-in. Your codebase name cannot be changed during beta â choose carefully.
- Vendor concentration. Code, PRs, and agents all in one company's hands. Git itself is portable, but PR history and review threads are not. Know your exit path.
- Hosting tied to a subscription. No free plan means your code hosting depends on keeping a Cursor subscription active.
- Privacy mode prerequisite. Teams still on legacy privacy mode must switch to Privacy Mode first; Origin follows the Privacy Mode of the namespace owner.
A 5-Step Evaluation Plan
1. Confirm your plan â Origin requires Pro, Teams, or Enterprise, and rolls out in stages.2. Claim your codebase name deliberately; you cannot rename it during beta.
3. Connect GitHub and sync one low-stakes repo; verify the mirror updates in real time.
4. Run a real PR through Cursor: comment, review from both sides, merge, and check the two-way sync holds.
5. Only then consider natively hosting a new project on Origin â and keep the exit path documented.