The Graphite Acquisition: Why It Explains Cursor Origin

On December 19, 2025, Cursor announced a signed definitive agreement to acquire Graphite, a code review platform Cursor's own announcement described as used by hundreds of thousands of engineers. Graphite's calling card is stacked pull requests: splitting one large change into small, dependent PRs that review faster, managed through its gt CLI, with a merge queue and an AI reviewer (Diamond) built around the workflow.

Context makes the price signal sharper. TechCrunch framed the deal as the third in an acquisition run, after the CRM startup Koala in July 2025 and recruiting firm Growth by Design that November, with Cursor itself valued at $29 billion as of November 2025. Paying a premium over a $290 million valuation for a review tool is a statement about how central the company thought review and merge would become.

In December the deal read as a tuck-in: an editor company buying a review tool. Cursor's announcement carried the tell, though. It argued that "as writing code has become faster, reviewing changes, merging them safely, and collaborating effectively have increasingly become the bottlenecks to building production-grade software," and teased integrations plus "some more radical ideas we can't share just yet."

The radical idea surfaced on June 16, 2026, when Tomas Reimers walked on stage at Compile and demoed Origin, a git hosting platform built by the Graphite team inside Cursor. In hindsight the acquisition was a hiring event for a forge. You do not pay a premium for a review company to keep running reviews on someone else's host; you do it because review, merge and hosting are one product when the traffic comes from agents. Graphite's own announcement had already named the destination: "one integrated platform where humans and agents create, review, and merge code changes collaboratively."

The strategy is a pipeline that keeps every stage of a change under one roof: write code in Cursor with agents doing more of the typing, review it with the patterns Graphite proved (small stacked diffs, a machine review pass before humans), and host plus merge it on Origin. Each Origin component has a different amount of history behind it, and that difference is what you should plan around.

This is the practical takeaway for anyone weighing Origin: the review layer is not speculative, because Graphite has run stacked review and a merge queue for years at real companies. The unproven part is the hosting underneath, which no one outside Cursor has used. A comparison of GitHub's stacking, Graphite and Origin makes the same split visible feature by feature.

Both companies answered directly, and in writing. Cursor's announcement: "Graphite will continue to operate independently with the same team and product." Graphite's own post: "Graphite's product and brand aren't going anywhere," with continued investment promised in the stacked PRs platform and merge queue, plans to combine Graphite's AI reviewer with Cursor's BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition., and integrations connecting local development, background agents and pull requests through 2026.

For teams using Graphite today, nothing needs migrating. The gt workflow still runs against GitHub, reviews and the merge queue work as before, and the acquisition has so far added resources rather than removed features. The open question is positioning: Graphite improves review on the host you already use, while Origin wants to be the host.