Build1 publisher2 min readPublished
Origin inherits GitHub's read list for every repo a developer syncs into Cursor
Cursor's new Git host keeps GitHub as the source of truth for synced repos while holding a browsable copy next to its agents. The only org-level control described at launch is an Enterprise opt-out.
The Engineer · Build desk

What happened
- Cursor launched Origin in early beta on August 17, 2026, a Git-compatible host with repositories, pull requests and code browsing inside the app, and its coding agents sitting next to every repo.
- Pull requests sync both ways on GitHub-connected repos, so a comment in Cursor posts to GitHub, replies appear in Cursor within seconds, and a review assigned on GitHub can be merged from inside Cursor.
- Vercel, Depot and Buildkite integrations are live at launch, with a Vercel preview deployment available per pull request and existing CI workflows running on Depot or Buildkite.
- Access is limited to paid plans, Pro, Teams and Enterprise, with no free tier, and the rollout is staged.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
- exposure Offboarding acquires a second surface: a read grant left in place on GitHub keeps working against the copy of the repo held inside Cursor.
- decision Picking an AI editor now settles where a second browsable copy of source code lives. That decision now sits with whoever signs off on code residency.
- constraint The opt-out belongs to Enterprise admins, so Pro and Teams customers have no org-level lever to point at in a review.
- cost There is no free tier, so every reviewer who needs to see a synced repo inside Cursor has to be a paid seat. The front end gets priced per head.
A user connects a GitHub account, picks an organization, and chooses which repos come across [3]. Cursor then holds a copy that can be browsed, searched and pulled from inside Origin, while pushes keep going to GitHub, which stays the source of truth for anything that started there [4]. Anyone with read or write access to a synced repo can view it in Cursor [5]. GitHub's existing team permissions therefore decide who sees the copy on Cursor's side [21].
Enterprise admins get an opt-out in admin settings [9]. Origin is on every paid plan and rolling out in stages [8]. A company that takes no action has it live on its paid seats [18], and the flow puts the sync in the hands of any developer with a GitHub account [20]. Creating a first repo also names the codebase, the organization's namespace, and that name lands in every repo URL in the form cursor.com/codebase/your-org [2].
Tomas Reimers, who co-founded Graphite before Cursor acquired it earlier in 2026 [12], said on Hacker News that Origin's features currently differ from GitHub "very little" [10], and that the team is "intentionally releasing this as a GitHub alternative where we meet them toe-to-toe on functionality" [11]. The pitch is co-location: repository, pull requests and coding agents in one product [13].
Origin is designed around the premise that agents are now a major source of commits, branches and pull requests [14]. If your agents open two pull requests a week, the saving from not cloning locally is small. Reviewers have to be willing to work in Cursor's pull request view; the two-way sync leaves both views open, since a comment made in Cursor posts to GitHub and a reply on GitHub appears in Cursor within seconds [6]. Preview deployments and CI only help teams already using the three vendors wired up on day one [7].
Cursor says the next steps are tooling to make sense of agent-written code and automation that pushes pull requests toward a mergeable state autonomously [15]. A repo where an agent can read everything and drive its own pull request toward merge needs branch protection and required reviewers settled first, wherever the source of truth lives.
Origin shipped on the same day GitHub had a worldwide outage of roughly eight hours [16]. It was also Cursor's first product launch as a fully owned SpaceX subsidiary, three days after the reported $60 billion deal closed on August 14, according to The New Stack [17].
What to watch
- Whether Cursor extends the admin opt-out beyond Enterprise to Teams and Pro, or adds per-repo approval before a sync can happen.
- Whether Origin gets branch protection of its own for Origin-hosted repos, or leans on GitHub's rules for synced ones.
- Whether any hosting feature appears in Origin that GitHub does not offer. That would change the migration case beyond co-location.