In recent years the practice of writing software has changed in ways that few anticipated even a short time ago.
AI tools have moved from occasional assistants to central participants in the development process. Agents can now generate substantial amounts of code, propose architectural changes, open pull requests, and iterate on feedback with limited human intervention.
This shift has placed new demands on the systems that store, review, and coordinate code.
Platforms originally designed for human teams working at a measured pace are increasingly asked to support workflows that move at machine speed and volume.
Git has remained the dominant version control system for more than a decade and a half, and GitHub has become the default place where most open source and commercial projects live. Its model of repositories, branches, pull requests, and reviews has shaped how developers collaborate. Yet the rise of AI coding environments has prompted some companies to examine whether that model needs adjustment when agents become primary contributors rather than occasional helpers.
Cursor is one of the better known tools in the current generation of AI coding platforms.
It provides an editor environment in which language models and agents can read, write, and modify code with varying degrees of autonomy. Until recently the actual storage of that code remained outside the product, typically on GitHub or similar services.
On August 17, 2026, Cursor introduces 'Origin,' a code hosting platform of its own.
According to the announcement, Origin allows users to create repositories that are hosted directly on Cursor's infrastructure.
It also supports the ability to connect existing GitHub repositories so that they appear inside the Cursor interface alongside any native Origin repositories.
When a repository is synced from GitHub, GitHub continues to serve as the source of truth. Pushes and other Git operations directed at the original remote still go there.
Origin maintains a continuously updated copy that can be browsed, searched, and used for pull request activity.
Pull requests form a central part of the new service. Users can open, review, comment on, and merge pull requests for both Origin-hosted and GitHub-synced repositories.
For repositories that remain connected to GitHub, comments and review actions made inside Cursor are reflected on GitHub, and activity that occurs on GitHub appears in Cursor within a short time.
The system is designed so that teams do not have to abandon existing GitHub workflows in order to use the new platform.
Beyond basic repository and pull request functions, Origin includes support for connecting external services.
Early integrations include Vercel for generating preview deployments on pull requests and promoting them to production upon merge, as well as Depot and Buildkite for continuous integration pipelines.
Additional integrations are expected over time. A command-line interface is available for standard Git operations such as cloning, pushing, and pulling.
The service is currently available in early beta to users on Cursor’s paid plans, including Pro, Teams, and Enterprise.
Access is being rolled out in stages, so not every eligible account sees the feature immediately. Free plan users do not have access at this time. Before a team can begin using Origin, a codebase name must be claimed.
That name becomes the namespace under which the team’s repositories are organized and appears in the URLs for those projects.
Cursor has described Origin as infrastructure built with agent scale in mind.
Agents operating inside the Cursor environment can interact directly with repositories hosted or mirrored on Origin. They can examine code, propose changes, update pull requests, and push branches without requiring the code to live exclusively on an external service.
This tighter coupling between the coding environment and the hosting layer is one of the more distinctive aspects of the product.
The appearance of Origin fits into a wider pattern in which companies that develop AI coding tools are beginning to expand into adjacent infrastructure.
Some observers view such moves as attempts to reduce dependence on established platforms. Others see them as efforts to create environments better suited to the particular patterns of agent driven development.
In the case of Origin, the product currently emphasizes compatibility with GitHub rather than a forced migration away from it. Whether that balance shifts over time will depend on how the platform develops and how development teams choose to organize their work.
During the announcement, Origin remains an early stage offering.
It's worth noting that the launch comes shortly after SpaceX completed its acquisition of Cursor’s parent company, Anysphere.
The deal, valued at $60 billion and structured entirely as an all-stock transaction, was first announced in a definitive agreement on June 16, 2026. It closed on August 14, 2026, a few days before Origin entered early beta.
Under the terms of the agreement, Anysphere shareholders received SpaceX Class A shares based on the $60 billion equity valuation. The transaction ranked among the largest acquisitions of a venture-backed company on record.
Cursor continues to operate under its own name as a wholly owned subsidiary following the close.
