AI Tools

What Is Cursor Origin, Cursor's New GitHub Alternative?

Published 2026-08-19 · Researched and price-checked on official sources

Cursor Origin is a code hosting service from Cursor, in early beta since August 17, 2026 on all paid Cursor plans. It adds repos, pull requests, code browsing, and GitHub sync to the editor, so you can host code and open PRs without leaving Cursor.

Key facts

What matters

Origin launched in early beta on August 17, 2026 and is included with all paid Cursor plans, from Individual at $20/mo to Teams at $40/user/mo.
The beta covers repos, pull requests, code browsing, and GitHub sync; agent-native features are promised next.
GitHub repos sit alongside Origin repos: connect GitHub, pick an org, and synced repos appear in Cursor's new Codebase tab.
Vercel, Depot, and Buildkite integrations are live, so pull requests get preview deployments and GitHub Actions workflows keep running.

What is Cursor Origin?

Cursor Origin is a code hosting service from Cursor, the AI code editor company, announced on August 17, 2026 and rolling out in early beta on all paid Cursor plans. Instead of hosting code on a separate platform like GitHub or GitLab, Origin keeps your repositories inside Cursor: you create a repo from the new Codebase tab, push with a CLI command, and browse code, review pull requests, and manage sync in the editor itself.

The launch post describes the first release as "designed for agent scale": repos, pull requests, code browsing, and GitHub sync are the essentials, with "agent-native features" promised to ship soon. Repo URLs follow the pattern cursor.com/codebase/<your-codebase-name>.

What does the Origin beta include?

Repos: create a repo from the new Codebase tab, then install the CLI and clone or push a local project. Push once and your code is hosted on Origin.
Pull requests and code browsing: the core review workflow, rendered inside Cursor instead of a separate web app.
GitHub sync: connect GitHub to Cursor, pick your org, and pull in the repos you want to sync. Your GitHub repos sit alongside the ones Origin hosts.
Repo settings: check sync status for GitHub repos, manage who has access, and see which apps are connected.

How Origin works with GitHub and your CI/CD

Origin is not a GitHub replacement in its current form; it is designed to sit next to GitHub. The sync feature means your existing repositories stay where they are while Cursor pulls in a working copy, which matters for teams that are not ready to move repositories anywhere.

For deployment and CI, the launch post lists three integrations that are already available, with more coming soon:

Vercel: connect it from a repo's Apps tab and every pull request gets a preview deployment you can test and comment on; merging ships to production.
Depot and Buildkite: both run your existing GitHub Actions workflows, and Buildkite also runs its native pipelines.

Cursor Origin pricing: what does it cost?

Origin has no separate price. It is included in all paid Cursor plans, which start at $20 per month. From the official Cursor pricing page, verified August 19, 2026:

Hobby: free, no credit card, limited Agent requests, Composer access. No Origin, because Origin is rolling out on paid plans only.
Individual: from $20 per month, with Pro, Pro+, and Ultra tiers.
Teams: from $40 per user per month, with Standard and Premium tiers, centralized billing, and agentic code reviews.
Enterprise: custom pricing, contact sales.

The practical read: Origin costs the same as your Cursor subscription. If you already pay for Cursor, code hosting is included at no extra cost. If all you need is hosting, GitHub's free tier is cheaper.

Cursor Origin vs GitHub: which should you use?

GitHub stays the default for most teams because of its maturity, ecosystem, and free tier. Origin is the choice for teams whose daily work already happens in Cursor and who want code, reviews, and AI agents in one surface. The table below summarizes what is verified on the official pages as of August 19, 2026.

Who should use Cursor Origin (and who should wait)

Try it now: solo developers and small teams who already pay for Cursor and want repositories next to their AI workflow, and who are comfortable with an early beta. The GitHub sync means you can test Origin without moving anything.

Wait: teams that depend on GitHub features the beta does not list. The announcement covers repos, pull requests, code browsing, and GitHub sync; everything else, including issue tracking, fine-grained permissions, and marketplace depth, is unconfirmed. Teams that need a free tier should stay on GitHub, because Origin requires a paid Cursor plan.

At a glance

	Cursor Origin	GitHub
Status	Early beta, rolling out since Aug 17, 2026	Mature, established platform
Pricing	Included in paid Cursor plans: Individual from $20/mo, Teams from $40/user/mo	Free $0/mo forever; Team $4/user/mo (first 12 months); Enterprise from $21/user/mo
Core features (beta)	Repos, pull requests, code browsing, GitHub sync	Unlimited repos, PRs, Issues, Code Review, Actions CI, Codespaces, Packages
CI/CD	Via Vercel, Depot, Buildkite integrations	Native GitHub Actions; free tier includes 2,000 CI/CD minutes/mo for public repos
AI	Cursor's agents; agent-native features ship soon	GitHub Copilot
Free hosting tier	No (paid plans only)	Yes, $0/month forever
Best for	Paid Cursor users who want code and AI in one surface	Teams that need the full platform and ecosystem

Cursor Origin vs GitHub, verified on official pages August 19, 2026

FAQ

Is Cursor Origin free?

No. It is rolling out in early beta on all paid Cursor plans: Individual from $20/mo and Teams from $40/user/mo, per the Cursor pricing page. The free Hobby plan includes Composer and limited Agent requests but not Origin code hosting.

Does Cursor Origin replace GitHub?

Not in the beta. Origin syncs with GitHub instead: connect GitHub, pick an org, and synced repos appear alongside Origin-hosted repos in the Codebase tab. The beta covers repos, pull requests, code browsing, and GitHub sync, and Cursor says agent-native features ship soon.

Can I run GitHub Actions with Cursor Origin?

Yes, through integrations. Depot and Buildkite both run your existing GitHub Actions workflows, and Buildkite also runs its native pipelines. Vercel can be connected per repo so every pull request gets a preview deployment.