Cursor Origin
Early beta on paid plans from 2026-08-17: Cursor hosts repos
Cursor changelog 2026-08-17: Origin begins rolling out today in early beta on all paid plans. Essentials: repos, PRs, code browsing, GitHub sync. Agent-native features ship soon. Enterprises can opt out. On 2026-08-27 Cloud Agents gained Start from scratch — no GitHub first, then save to Origin. QCode does not host your git.
Four facts you can quote
Origin starts rolling out
Changelog title: Origin code hosting. Early beta on paid plans; enterprise admins can opt out.
The starting four
Official: repos, pull requests, code browsing, and GitHub sync. For repos started on GitHub, GitHub stays source of truth; pushes still go there.
Codebase name in the URL
The name of your first codebase becomes part of the URL: cursor.com/codebase/<name>. The CLI snippet shows clone / push.
Start from scratch
Cloud Agents no longer require GitHub first. Prompt, then Create repo on Origin. Live preview via port-forward; publish needs Vercel.
This is Cursor hosting git, not another Auto pricing page
The site already covers Cursor’s two usage pools, Auto pricing, and the 3-agents window. Origin answers a different sentence: the editor vendor now hosts git. GitHub-synced repos keep two-way PR comments; Cursor-hosted repos live on Origin. Early beta is paid plans; the announce does not name the free tier.
08-27 adds “you can start with no remote”
The 17th Origin note still assumed clone/push. Start from scratch on the 27th: pick the repo picker, prompt immediately, Cursor creates an Origin repo in the background, then Create repo when you like it (private or internal). That splits Cloud Agent cold-start from “bind GitHub first.” Still a Cursor product, not a generic git-host review.
Timeline
cursor.com/changelog/origin-code-hosting: paid-plan early beta. Codebase tab, GitHub sync, PRs, Vercel / Depot / Buildkite apps.
Cloud-agent subscriptions, /goal, subagents on their own machines — adjacent to Origin, not hosting itself.
Start from scratch: Cloud Agent without a third-party SCM, then save to Origin. Rechecked 2026-08-30 still early beta.
Confirmed vs rumor
Confirmed
Paid-plan early beta, enterprise opt-out, starting four, GitHub remains source of truth for synced repos, 08-27 GitHub-free cold start — cursor.com/changelog, fetched 2026-08-30.
Rumor
“Cursor already replaces GitHub” — they wrote essentials, agent-native soon, early beta. “Free users get Origin” — the announce said all paid plans. “QCode hosts Origin” — QCode does not host repos.
Stay on GitHub vs try Origin
GitHub stays the main remote
Synced repos still push to GitHub. Fits teams whose CI, ACL, and compliance already live there. Origin is then a browse + agent mirror.
Cursor-hosted Origin repos
Fits greenfield, or the 08-27 blank-prompt Cloud Agent. Visibility private / internal. Enterprises: check whether admin opted out.
How to enter the beta (official product path)
Paid Cursor plan, open Codebase, +New or Start from scratch. Follow the on-page CLI for clone/push. This page does not describe unauthorized mirroring of private repos. Model calls and code hosting are separate: API keys you already have, git still on Cursor / GitHub.
QCode does not host Cursor Origin
Origin is Cursor’s code-hosting beta. QCode sells a model API; it does not store your git. Which model a Cloud Agent uses is Cursor’s product bill. If you move the agent to your own API, use an already-provisioned key at official price × service fee; the repo still follows GitHub or Origin as you chose.
FAQ
Who gets Origin?
Changelog: early beta on all paid plans; enterprises may opt out. Trust the account and admin setting.
After GitHub sync, where is source of truth?
Official: Pushes keep going to GitHub, which stays the source of truth for anything started there.
Do I still need GitHub after 08-27?
Start from scratch says Cloud Agents no longer require GitHub or another SCM first. Prompt, then save to Origin.
Is it a general-purpose git host?
Official positioning is essentials for agent scale, early beta. Do not demand GitHub.com’s full compliance checklist.
What does publish need?
08-27: a Vercel account for publish. That is Cursor’s publish feature, not QCode.
Can QCode create an Origin repo?
No. That is the Cursor console. QCode is a model API only.
Sources
https://cursor.com/changelog/origin-code-hosting (2026-08-17) and https://cursor.com/changelog/start-from-scratch (2026-08-27). Docs: cursor.com/docs/origin. Fetched 2026-08-30.
Code can live on Cursor Origin; models can be a separate API
QCode does not host git. For your own models, official price × service fee on ids that are sold.
Related
Cursor 3-agents window
Agent count and windows on the same product — not code hosting.
Cursor Auto pricing
August 2026 billing news, a different question from where the repo lives.
Cursor two usage pools
How quota splits — keep it apart from “where is the code.”
Reading of Cursor’s public changelog. Early-beta scope follows your account. QCode does not host Origin and does not bypass Cursor or GitHub permissions.