News · 2026-08-17

Cursor built its own GitHub

Cursor now hosts your code. The company shipped Origin, a git forge built into its AI coding platform, and the documentation describes it plainly: "Origin is Cursor's git forge for storing and sharing code." In early beta you can create repositories, push and pull with standard git, mirror a GitHub repository into Origin, browse and search code in a browser, and open, review and merge pull requests. It is available on Pro, Teams and Enterprise plans, and not on free ones.

Key facts

• Origin is live in early beta with repository creation, git push/pull, GitHub mirroring, pull requests, code browsing and search, and third-party integrations with Vercel, Depot and Buildkite.
• "Origin code storage is available on Pro, Teams, and Enterprise plans. It is not available on free plans," per Cursor's documentation. Access opens in stages.
• Cursor has published no standalone Origin price; the public plan anchors are Pro at $20 a month and Teams at $40 per user per month, per Cursor's pricing page.
• Announced by CEO Michael Truell alongside Tomas Reimers, Product Lead for Origin, at the company's Compile conference in June 2026, where it was billed as "a new Git platform."

The detail that tells you this is a shipped product rather than a teaser is where it was announced: a documentation page, complete with setup instructions, an admin disable switch, and a note about which privacy modes are incompatible. Companies do not write "Teams on legacy privacy mode cannot enable Origin, so switch to Privacy Mode first if you want access" about vaporware.

What Cursor is doing here is moving up-stack. For two years the company's product was the place code gets written. Origin is a bid to also be the place code gets stored, reviewed and merged. The stated rationale, from the Compile keynote framing, is that code is now being produced faster than the infrastructure built to handle it -- and the infrastructure in question is the pull request, a workflow designed around the assumption that a human wrote the diff and another human will read it. When an agent opens fifteen pull requests before lunch, the bottleneck stops being authorship and becomes review.

Think of it as a print shop that just bought the warehouse next door. The printing was never the constraint; the constraint was what happens to the pallets afterward. Cursor already has cloud agents, automations, PR routing and approval, and a code-review product in Bugbot. Origin is the missing floor underneath all of it -- and, not incidentally, the piece that would otherwise keep every Cursor customer's most valuable asset sitting on a competitor's servers.

The feature list is deliberately unsurprising. Repositories live under a claimed namespace at a URL of the form cursor.com/codebase/{owner}/{repo}. Any team member can claim the namespace; admins grant repository access and can disable Origin for the whole team from the dashboard. You can create repositories from Cursor agents directly, sync existing ones over from GitHub, and connect Vercel, Depot and Buildkite from repository settings. There is an Origin CLI for terminal workflows. Privacy follows the Privacy Mode of whoever owns the namespace. None of that is novel as forge functionality; all of it is table stakes that a forge has to have before anyone will move a repository onto it.

The question worth asking is whether this changes what a coding agent can actually do, and on the published evidence the answer is no. Origin ships no new model, no new autonomous primitive, and nothing that Claude Code or Codex could not already accomplish against a GitHub repository. What it changes is ownership of the surface where agent output gets judged. That is a strategic move rather than a capability move, and it is the same move several parts of the industry are making at once -- if agents are going to write most of the code, whoever owns the review layer owns the leverage. Practitioner reaction on Hacker News has run along predictable lines: appreciation for Cursor's repository-aware workflow, alongside recurring questions about how many products Cursor is now running at once and whether simpler command-line tools are easier to trust.

The caveat is the ordinary one for early-beta infrastructure. Cursor is asking teams to put source code -- the single asset a software company least wants to migrate twice -- into a forge that is weeks old, staged in rollout, has no published standalone price, and comes from a company whose core business is something else. GitHub mirroring is the sensible hedge and Cursor supports it, which is probably how most teams will touch Origin for the next year: mirror in, evaluate, and keep the original where it is.

Primary source, verified: read the paper →

Ground Truth. (2026, August 17). Cursor built its own GitHub. Ground Truth. https://groundtruth.day/news/cursor-built-its-own-github.html

@misc{groundtruth:cursor-built-its-own-github,
  title  = {Cursor built its own GitHub},
  author = {{Ground Truth}},
  year   = {2026},
  month  = {aug},
  url    = {https://groundtruth.day/news/cursor-built-its-own-github.html}
}

Topics: developer-tools · coding-agents · product-launch · cursor · git