Cursor Origin launched 17 August 2026 with 3 unanswered governance questions

Summary. Cursor began rolling out Origin, its own git forge, on 17 August 2026 in early beta to Pro ($20/mo), Teams ($40/user/mo Standard, $120/user/mo Premium) and Enterprise plans, and to the India-only Start plan at ₹649/mo. Free plans are excluded. Three days later, three questions a platform team has to answer before adopting it are still unanswered in Cursor's own documentation: two doc pages disagree on whether any team member or only an admin can claim your organisation's permanent namespace; Origin appears on none of the three pages that price Cursor; and no page describes retention, residency, or an export path for repositories that live only on Origin. The last time Cursor shipped at this pace was 13 August 2026 (Builds) and 19 August 2026 (agent subscriptions), so the docs are moving too. Read them again before you decide.

What actually shipped, and when

The Origin changelog entry dated 17 August 2026 is short and specific: "Origin begins rolling out today in early beta on all paid plans. We're starting with the essentials, designed for agent scale: repos, pull requests, code browsing, and GitHub sync."

The Origin overview docs put it more plainly: "Origin is Cursor's git forge for storing and sharing code." Repositories live under a namespace at cursor.com/codebase/{owner}/{repo}, and clone URLs resolve to origin.cursor.com/{owner}/{repo}.git. In early beta you can create repos, push and pull with standard git, mirror a GitHub repository, open and merge pull requests, and connect Vercel, Depot or Buildkite from repository settings.

That arrived inside a nine-day run of releases. On 13 August 2026 Cursor shipped Builds, pre-warmed environment snapshots for cloud agents, claiming internally "10x faster" environment boots and "3x faster time to first token," included with Cloud Agents at no additional cost. On 19 August 2026 cloud agents gained event subscriptions, subagents on isolated virtual machines, and a /goal command that holds an objective across a long session. Origin is the storage layer under that; the agents were always going to need somewhere to push. If you are already running event-triggered coding agents, Origin is the piece that closes the loop.

Question 1: who claims your namespace, and can you ever change it?

This is the sharpest problem, and it is a contradiction between two Cursor pages that link to each other.

The Origin overview says: "Any team member can claim the codebase name: open cursor.com/codebase, select Get Started, and follow the setup flow."

The codebase settings page says: "A team admin claims the codebase name and enables Origin; non-admins can request access from the same page."

Both were live on 20 August 2026. One says any member; the other says admins only. The codebase-settings page links to the overview as the authority on claiming, and the overview is the one that says any member can do it.

Why it matters is the next sentence in the overview: "During the beta, you can't change or update your namespace after it's claimed. Choose your codebase name carefully."

So the worst case, if the overview is the accurate page, is that a single engineer on a Pro seat claims acme for your organisation, gets it wrong, and the name is frozen for the duration of the beta. The docs describe no rename, no transfer and no deletion. The only teardown control documented anywhere is one line, repeated on both pages: "Admins can disable Origin for the team at any time from the dashboard." Disabling is not described as releasing the claimed name.

The practical move, today, before anyone on your team opens cursor.com/codebase: decide the namespace yourself, claim it deliberately, and then use codebase settings to grant repository-creation rights. Treat it the way you would treat an npm org or a DNS zone, not a settings toggle.

Question 2: nobody has priced it

Origin does not appear on cursor.com/pricing. It does not appear in the plan table on Cursor's models and pricing docs. It does not appear on the Teams pricing page. No storage tier, no per-repo charge, no bandwidth line, no "included in" bullet.

The only access statement is in the overview: "Origin code storage is available on Pro, Teams, and Enterprise plans. It is not available on free plans." Meanwhile the create-repository page states the gate without naming a plan at all: "You need access to Origin code storage for the create to succeed."

Here is what those plans do cost, as published on 20 August 2026:

Plan	Published price	Third-party model usage included	Origin listed on the pricing page?
Hobby	Free	None	No, and the overview excludes free plans
Start (India only)	₹649/mo, tax inclusive	$0	No
Pro	$20/mo	$20	No
Pro Plus	$60/mo	$70	No
Ultra	$200/mo	$400	No
Teams Standard	$40/user/mo	Pooled, on-demand on by default	No
Teams Premium	$120/user/mo	5x a Standard seat	No
Enterprise	Custom, contact sales	Per-member limits available	No

An unpriced beta feature is normal. An unpriced storage feature is a budgeting problem, because storage costs accrue whether or not anyone is looking, and because the thing you would migrate off later is your source of truth rather than a chat history. Cursor also charges a Cursor Token Rate of $0.25 per million tokens on third-party model requests for Teams and Enterprise, including BYOK, and a 10% uplift for regional data residency on model pricing. Neither line is stated to cover, or not cover, Origin repository storage. If you are already modelling Cursor Teams seat mix against usage, leave a line item open for this one.

Question 3: the mirror is not a backup, and detaching is one-way

The mirror documentation is clear about direction, and clearer than most people reading the launch post assumed. "Mirroring copies a GitHub repository into Origin and keeps Origin updated as the GitHub repo changes." Code is not read-only on the Origin side: "You can push too: pushes to a synced repo pass through to GitHub, which remains the source of truth."

What syncs, and what does not:

Artifact	Mirrored repo (from GitHub)	Origin-native repo
Git history, branches, tags	Synced into Origin	Origin only
Pushes	Pass through to GitHub	Stay on Origin
Pull requests	Sync in both directions	"They are not mirrored anywhere"
GitHub Issues	Not included	Not applicable
GitHub Actions workflows and secrets	Not included; "CI configuration stay on GitHub"	Depot or Buildkite instead
Depot and Buildkite CI	Not supported on mirrored repos	Supported
Branch protection, webhooks	Docs silent	Docs silent

Two consequences follow. First, a repository created directly on Origin has no GitHub copy at all, and its pull requests, in Cursor's own words on the pull requests page, "are not mirrored anywhere." Your review history for that repo exists in one place. Second, the escape hatch runs the wrong way. The settings page documents "Detach from GitHub" under a Danger Zone: "This stops the sync and converts the Origin copy into a standalone Origin-hosted repository: Origin becomes the source of truth, and pushes to the Origin remote no longer flow to GitHub." There is no documented inverse operation that promotes an Origin-native repo into GitHub.

Mirroring also has real prerequisites that will stop a casual trial: the Cursor GitHub app connected to the owning org, and GitHub admin access on the repository you want to sync. A developer without repo-admin on GitHub cannot mirror. A developer with a Pro seat can still create Origin-native repos.

Note the CI asymmetry too. Depot and Buildkite "work on Origin-hosted repositories only, not on repos mirrored from GitHub. Mirrored repos keep CI on GitHub." So the moment you move a repo fully onto Origin, you also move your CI, which is the same class of migration work covered in a GitLab to GitHub Enterprise Importer migration: the code moves in an afternoon and the pipelines take a quarter.

What Cursor does say about privacy, and where it stops

Origin does not define its own data posture. The overview says: "Origin follows the Privacy Mode of the namespace owner: the team or the individual who owns the repo." That matters because of the previous section. If an individual claims the namespace, the individual's Privacy Mode governs the repos, not your organisation's.

Cursor's privacy help page defines the guarantee narrowly and honestly: "Privacy Mode ensures your code is never used for training by Cursor or other AI model providers." It is on by default for Enterprise teams, and "Teams and Enterprise admins can enforce it organization-wide so members cannot disable it." Training is not retention. Retention sits under zero data retention, which carries two stated carve-outs: "ZDR doesn't apply when you use your own API keys," and "Some models also require data retention with their provider and fall outside Cursor's ZDR agreements. These models are off by default and require admin approval before use."

Then there is a gate the docs never define. Both Origin pages say, in identical words, that "teams on legacy privacy mode cannot enable Origin, so switch to Privacy Mode first if you want access." The privacy page they link to for the fix does not contain the phrase "legacy privacy mode" anywhere. If your team is on it, the docs tell you that you are locked out and do not tell you what you are on or what changes when you switch.

On the security side, Cursor's security page, last updated 24 April 2026, states that "A SOC 2 Type II attestation report is available on request at trust.cursor.com," commits to "at-least-annual penetration testing by reputable third parties," publishes its subprocessor list on the trust portal rather than inline, and says: "Cursor does not use or maintain any infrastructure in China. We do not use any companies headquartered in China as subprocessors, and to our knowledge none of our subprocessors do either." Customer Managed Encryption Keys are described as covering "embeddings and Cloud Agent data." Repository storage is not named in that scope.

None of this is an accusation. It is an inventory of what an early beta has published so far, and the answer to "can we put our source code there" depends on the parts that are missing rather than the parts that are written.

India-specific considerations

Two details land differently for teams operating under the Digital Personal Data Protection Act 2023. Cursor's regional data residency option is described as a 10% uplift on model pricing; nothing on any page extends that to Origin repository storage, and no region is named for where Origin repos sit. Second, the India-only Start plan at ₹649/mo, tax inclusive, is not listed among the plans that include Origin code storage, and its docs entry excludes several other paid features, so an Indian team standardising on Start should assume no code hosting until Cursor says otherwise.

Source code containing personal data, or configuration containing production credentials that reach personal data, pulls the hosting question into your DPDP record-keeping. The practical answer for now is the boring one: mirror rather than migrate, keep GitHub as the source of truth, and revisit when residency and retention are published.

What to do this week

Claim the namespace deliberately, at admin level, before someone claims it for you, because it cannot be renamed during the beta. Keep every repository that matters mirrored rather than Origin-native, so GitHub stays the source of truth and you keep Actions and Issues. Do not move CI to Depot or Buildkite yet, because that step is what makes the mirror one-way in practice. Ask Cursor, in writing, for Origin retention, residency, deletion and export terms before any repo goes Origin-native. And treat every claim in this article as dated: all of it was read on 20 August 2026, on pages that carry an "early beta" banner and have changed three times in the last nine days.

The real cost is usually the migration, not the code. Origin makes the first half free and does not yet document the second half.

FAQ

When did Cursor Origin launch and what stage is it at?

Cursor began rolling Origin out on 17 August 2026, described in its changelog as an early beta on all paid plans. Every Origin documentation page carries an early beta banner. In this stage you can create repos, push and pull with git, mirror GitHub repositories, browse code, and open and merge pull requests.

Which Cursor plans include Origin code hosting?

The Origin overview states that Origin code storage is available on Pro, Teams and Enterprise plans and is not available on free plans. The create-repository page states the gate without naming any plan. No Cursor pricing page lists code hosting as a feature of any tier, so treat plan coverage as unconfirmed.

Does mirroring a GitHub repository into Origin back it up?

No. Mirroring copies git history, branches and tags into Origin and keeps pull requests in sync both ways, but GitHub Issues and GitHub Actions workflows and secrets are explicitly not included. Pushes to a mirrored repo pass through to GitHub, which Cursor states remains the source of truth for that repository.

Can an Origin namespace be renamed or transferred?

Not during the beta. The Origin overview states that you cannot change or update your namespace after it is claimed, and advises choosing the codebase name carefully. The docs describe no rename, transfer or deletion path. The only related control documented is an admin toggle that disables Origin for the team.

What happens if I detach an Origin repository from GitHub?

Detach from GitHub sits in a Danger Zone in repository settings. Cursor states it stops the sync and converts the Origin copy into a standalone Origin-hosted repository, making Origin the source of truth, after which pushes to the Origin remote no longer flow to GitHub. No documented inverse operation promotes an Origin-native repo back to GitHub.

Does Privacy Mode cover code stored on Origin?

Origin follows the Privacy Mode of the namespace owner, meaning the team or individual who owns the repository. Privacy Mode is defined as ensuring code is never used for training by Cursor or model providers. That is a training guarantee, not a retention guarantee, and retention sits separately under zero data retention with stated carve-outs.

How much does Cursor cost across its plans in August 2026?

Cursor publishes Pro at $20 a month, Pro Plus at $60, Ultra at $200, and an India-only Start plan at ₹649 a month tax inclusive. Teams seats are $40 per user a month Standard and $120 per user a month Premium. Enterprise pricing is custom. None of those pages price Origin storage.

What should a platform team do about Origin right now?

Claim the namespace deliberately at admin level, since it cannot be renamed during the beta. Keep important repositories mirrored rather than Origin-native so GitHub remains the source of truth and Actions and Issues survive. Hold CI on GitHub. Request retention, residency, deletion and export terms in writing before any repository becomes Origin-native.

How eCorpIT can help

eCorpIT runs AI coding agent rollouts as a governed programme rather than a tool purchase, covering namespace and identity decisions, source-control policy, and the CI ownership questions that surface the moment a second forge appears. Our AI coding agent rollout governance work and our enterprise agent-host policy practice both start from what the vendor documentation does and does not commit to. We are CMMI Level 5, MSME Certified and ISO 27001:2022 certified, and we design engineering platforms aligned with DPDP Act 2023 requirements. Talk to our senior engineering team via /contact-us/.

References

1. Origin Code Hosting, Cursor changelog, 17 August 2026
2. Origin overview, Cursor Docs
3. Origin codebase settings, Cursor Docs
4. Mirror a GitHub repository, Cursor Docs
5. Origin pull requests, Cursor Docs
6. Origin repository settings, Cursor Docs
7. Create an Origin repository, Cursor Docs
8. Cursor pricing
9. Cursor models and pricing, Cursor Docs
10. Cursor Teams pricing, Cursor Docs
11. Privacy and Privacy Mode, Cursor Help
12. Cursor security, last updated 24 April 2026
13. Cloud Agents and Cursor Harness Improvements, Cursor changelog, 19 August 2026
14. Cloud Agents Start 3x Faster with Builds, Cursor changelog, 13 August 2026

Last updated: 20 August 2026.