Cursor Now Hosts Your Code: Origin Takes On GitHub, Live for All Paid Plans

The AI code editor now wants to be your GitHub.

On 2026-08-17, Cursor shipped Origin — its own code hosting service. The announcement opens bluntly: “Cursor can now host your code.” This isn’t a side experiment either. Early beta went out that same day to every paid plan, except enterprise organizations whose admins opt out.

Here’s what actually ships today, how to start, how it coexists with your existing GitHub, and the one line worth paying attention to. (All details from the official Cursor changelog dated 2026-08-17; last checked 2026-08-20, official page returned HTTP 200 on direct fetch.)

The short version: this release is plumbing, not fireworks

Cursor says it started “with the essentials, designed for agent scale” — four things:

1. Repos
2. Pull requests
3. Code browsing
4. GitHub sync

Then this: “Agent-native features ship soon.” In other words, what you can see today is the foundation. The things that would actually differentiate Origin from GitHub haven’t landed yet. This release is mostly about getting the code in the room.

Getting started: the Codebase tab

The official flow:

1. Open the new Codebase tab — home for Origin repos.
2. Click +New, create a repo, name it.
3. A page appears showing how to install the CLI, with commands to clone a repo or push a local project.
4. Push, and your code is hosted on Origin.

One detail worth thinking about before you click: the name you give your codebase becomes part of every repo URL, in the form cursor.com/codebase/your-name (the official example is acme-corp). That’s effectively your org namespace — pick it deliberately.

Coexisting with GitHub: GitHub stays the source of truth

The design here is coexistence, not migration:

• GitHub repos sit alongside the ones Cursor hosts.
• Connect GitHub, pick your org, and you see which repos can sync. Select one and Cursor pulls it in.
• You choose what gets synced, and you can disconnect a repo at any time.
• Anyone with read or write access to a synced repo can view it in Cursor too.
• Synced repos update in real time — browse, search, and pull from the Origin copy.
• Pushes keep going to GitHub, which the changelog states plainly remains the source of truth for anything started there.
• Icons next to each repo name show which are Cursor-hosted and which came from GitHub.

Pragmatic: it doesn’t force you to move. Origin can simply be a second copy that’s visible and agent-accessible, with GitHub still underneath if anything goes wrong.

Two-way PR sync is the sleeper feature

Every repo has pull requests. Open one and you get the timeline, commits, checks, and files changed. Review the diff, leave comments, merge.

The useful part is that PRs on synced repos sync both ways:

• Comment in Cursor → it posts to GitHub.
• Someone reacts or replies on GitHub → it appears in Cursor within seconds.
• Assigned a review on GitHub? Review and merge it from Cursor.

Which means your teammates don’t have to change tools or even know you switched. If you’re the only person on the team who wants to move, this is the feature that makes it possible.

Agents live inside every repo

Short section in the changelog, but it’s the whole point: your code, PRs, and agents are now in the same place.

Ask Cursor about code you’re browsing and it can answer, make changes, update PRs, or push a branch.

The old loop was: prompt the agent in the editor → commit yourself → open a PR → review it on GitHub. That loop is now collapsed. It also explains the phrase “designed for agent scale” — with many agents running at once, context-switching cost compounds.

Integrations available now: Vercel, Depot, Buildkite

Cursor says it’s building an app ecosystem; three integrations are live:

• Vercel — connect it from a repo’s Apps tab and every PR gets a preview deployment you can test and comment on. Merge and it ships to production.
• Depot — CI.
• Buildkite — CI.

Worth noting: both Depot and Buildkite run your existing GitHub Actions workflows, and Buildkite also runs its own native pipelines. Your CI config doesn’t need rewriting.

Each repo also has a settings page for GitHub sync status, access management, and connected apps.

Who can use it today

All paid plan users, as of 2026-08-17 — the only exception being enterprise orgs whose admins opt out.

Put differently: Cursor’s free tier does not get this. (Full free-vs-paid breakdown on our Cursor tool page.)

Should you jump in now?

This is an early beta by Cursor’s own description, with agent-native features explicitly still to come. Three practical suggestions:

• Don’t make Origin the only copy of anything. Cursor’s own design keeps GitHub as source of truth — no reason to be more aggressive than the vendor.
• Sync one non-critical repo first. Disconnecting is supported, so the cost of trying is near zero.
• Watch whether two-way PR sync holds up. It’s the most concrete value on offer today and the most likely thing to break — if it’s reliable, one person can switch tools without disrupting the team.

The thing actually worth waiting for is that “ship soon” line. This release puts the code and the agents in the same room. The next one will tell us what they can do in there.

Verified 2026-08-20. Source: the official Cursor changelog, Origin Code Hosting (2026-08-17). Features and availability are in early beta and may change; the official announcement is authoritative. Cursor plan and free-tier details on our Cursor tool page.