Cursor co-founder and CEO Michael Truell (@mntruell) launched Origin on August 17th, moving the AI coding company into repository hosting, pull requests and the infrastructure used to ship the code its agents produce.
https://x.com/cursor_ai/status/2089399057659596847 Cursor said in a three-post thread on X that Origin was beginning a staged beta rollout with integrations for Vercel, Buildkite and Depot. The initial release is available across Cursor's paid plans, although access is opening in stages and enterprise administrators can disable it.
Truell founded Cursor with Aman Sanger, Arvid Lunnemark and Sualeh Asif around a thesis that AI would change the interface developers use to understand and edit software. Origin extends that thesis beyond the editor. Cursor now wants to control where code lives, how agents interact with it and the path from an agent-generated change to a merged pull request.
A bridge from GitHub
Origin can host new Git repositories directly. Developers create a repository in Cursor's Codebase tab, install the Origin command-line interface and use standard Git commands to clone, push and pull projects, according to Cursor's launch notes.
Cursor also built the beta around GitHub migration rather than demanding an immediate move. Users can connect a GitHub organization and select individual repositories to mirror into Origin. Those copies update in real time, while GitHub remains the source of truth for repositories that began there. Developers continue pushing to GitHub and can disconnect the mirror.
That bridge lowers the cost of testing Origin inside an existing engineering organization. Repository hosting is difficult to displace because code, permissions, deployment systems and years of workflow automation accumulate around the incumbent platform. Cursor is letting teams add its interface and agents around GitHub before asking them to host code with Cursor itself.
Pull requests on mirrored repositories also sync in both directions. A comment posted from Cursor appears on GitHub, while replies and reactions made on GitHub are reflected in Cursor. Origin exposes the pull-request timeline, commits, checks, changed files, review comments and merge controls.
The central product difference is the agent. From a repository page, users can ask Cursor questions about the code, request changes, update a pull request or push a new branch. Cursor's Origin documentation says agents can also create repositories and connect automations to Origin-hosted projects.
Cursor moves closer to the shipping layer
Origin was previewed at Cursor's Compile conference in June, where Truell appeared with Tomas Reimers, Cursor's product lead for Origin. Reimers was one of the founders of code-review startup Graphite, which agreed to join Cursor in December 2025.
That background matters because Origin puts Cursor directly into review and merge workflows, the category Graphite spent years building around. Cursor said when it announced the Graphite deal that Graphite would continue operating independently. Graphite subsequently added Cursor Cloud Agents to its own pull-request interface, allowing developers to start an agent, review its work and merge the resulting change from the browser.
Origin now gives Cursor a native repository and pull-request surface alongside that Graphite integration. The overlap shows how Cursor is assembling an end-to-end development platform: agents generate changes, repositories store them, review tools inspect them and deployment or continuous-integration services run them.
Vercel can create preview deployments for Origin pull requests and send merged changes to production. Depot and Buildkite provide continuous integration; both can run existing GitHub Actions workflows, while Buildkite also supports its own pipelines. Those integrations give early users a workable shipping path without requiring Cursor to rebuild every adjacent developer service.
The beta remains narrow. Cursor describes Origin in its documentation as an "early access research preview." Free accounts cannot use Origin storage, access may not appear immediately for eligible customers, and teams using Cursor's legacy privacy mode must change privacy settings before enabling it. Cursor says more agent-specific features are planned, without detailing them in the launch announcement.
Origin's launch strategy reflects the position Cursor occupies. Developers already use Cursor agents to create branches and pull requests, but the resulting work typically lands in infrastructure controlled by another platform. Hosting the repository gives Cursor persistent access to the code, review history and agent activity that shape subsequent work. It also gives Truell a route to turn an AI editor into the primary system through which software teams create and ship code.