Summary: Cursor launched Origin code hosting in early beta for paid plans on August 17, 2026, with repos, pull requests, browsing, and GitHub sync. GitHub repositories can be synced without migration, while Vercel, Depot, and Buildkite integrations support previews and existing CI workflows. Together with Builds and the SpaceX acquisition, the article frames Origin as part of an agent-scale development stack.
The Shift: Cursor Hosts Your Code
On August 17, 2026, Cursor’s changelog carried a single sentence: “Cursor can now host your code.” That marks the arrival of Origin, a code hosting service in early beta for every paid plan. It’s a meaningful move: a company whose reputation rests on an AI-powered editor is walking onto ground GitHub has held for years. Yet Origin is not one more place to park repositories. It was designed from the ground up around agent scale—the features put how AI agents work with code first, not only how people do.
What ships at launch is the essentials: repos, pull requests, code browsing, and GitHub sync. Agent-native capabilities are promised soon. The insight worth catching is that code, PRs, and agents now share one interface. Browsing a repo, you can put a question to Cursor, have edits made, refresh an existing PR, or push a new branch. For a human that’s convenient. For an agent it’s a native working environment—reading, reviewing, executing, and delivering no longer require a trip across three separate systems.
The launch doesn’t stand alone. August 13 brought Builds, aimed at shortening cloud agent startup. August 14 brought word that SpaceX had officially acquired Cursor, handing it the world’s largest GPU fleet. Read together, the three pieces stack vertically: Origin decides where code lives, Builds readies the execution environment, and SpaceX supplies the compute. Call it a roadmap for pulling the whole agent workflow under one roof.
Inside Origin: Repos, PRs, and the Codebase Tab
A new Codebase tab is home for your Origin repos. To make one, you click +New, give it a name, then follow the setup to install the CLI and push a local project. Creating your first repo also asks you to name the codebase, and that name becomes part of every repo URL—cursor.com/codebase/acme-corp, for instance. The scheme hints at what Cursor wants: the codebase is treated as a first-class concept rather than an entry in a list of repositories.
Pull requests arrive fully equipped. Every repo has a PR view carrying timeline, commits, checks, and files changed, so diffs can be reviewed, comments left, and merges performed without leaving Cursor. For repos synced from GitHub, PRs flow in both directions: a comment you write in Cursor posts to GitHub, while a reply or reaction on GitHub shows up in Cursor within seconds. Assign a review to yourself on GitHub and you can finish and merge it from Cursor as well.
GitHub Sync: Try It Without Migrating
For teams weighing a new code host, migration is the loud question: what becomes of history, CI, permissions? Origin answers with two parallel tracks. Connect your GitHub account, pick an org, and bring selected repos into Origin. Those synced repos sit beside Cursor-hosted ones, with icons showing which is which. Synced repos stay current in real time—you browse, search, and pull from the copy in Origin, while pushes continue to GitHub, which remains the source of truth for anything that started there. Any repo can be disconnected whenever you like.
The practical upshot is a trial with zero migration cost. Wire up GitHub, watch how agents perform while PR context is available, and postpone the decision about whether new projects should begin life in Origin. Nobody is being pushed to choose a side—the contest runs at the experience layer, not the data layer.
App Extensions: CI and Previews, Wired In
An app ecosystem launches alongside Origin. Integrations with Vercel, Depot, and Buildkite are live already, and more are on the way. Link Vercel from a repo’s Apps tab and each PR receives a preview deployment you can exercise and comment on; merge, and it ships to production. For CI, wire in Depot or Buildkite—either runs the GitHub Actions workflows you already have, and Buildkite additionally supports its own native pipelines.
That dissolves much of the fear about redoing your CI after a hosting switch. Workflows carry over; what changes is who supplies the execution environment. For agent workflows the effect runs deeper than for human ones: with a preview deployment hanging off every PR, each change an agent produces lands somewhere it can actually be exercised, and a reviewer looks at running software rather than reconstructing it from a diff.
The Context: Builds, and the SpaceX Deal
Two other announcements explain Origin’s timing. The first is Builds, introduced August 13—ready-to-use copies of your development environment, prepared continuously in the background at no extra cost. By default Cursor produces a fresh build every hour. Starting an agent boots it into a prepared environment with repos cloned, dependencies installed, and the install script already executed, so sessions come up nearly instantly and responses run up to 3x faster.
Builds also add resilience. Cloud agents always launch from the newest successful build. Should a dependency bump break your install script, or a Docker build fail, that build never goes active and you are notified. Sessions already running, and new ones, carry on safely while you debug in the background. Builds can be inspected in the Cloud Agents dashboard, logs and commit SHAs included, and agents themselves can manage builds through the Cursor Cloud MCP.
Internally, Cursor reports environments booting 10x faster and time to first token 3x faster. Customer Faire runs more than 2,000 automated agent runs each week, and its largest, most complex repos start in seconds. As of August 17, every environment, new or existing, uses builds by default at no additional cost.
The second announcement landed August 14: SpaceX formally completed its acquisition of Cursor, a process that began in April with a model-training partnership with SpaceXAI. Access to the world’s largest GPU fleet will let Cursor build stronger models that cost less to run. Grok 4.6, released August 12, is offered as an early look at what the two can produce together.
What to Do Now, and What Gives Pause
If Cursor cloud agents already carry a lot of your work, Origin is worth opening today: it comes on all paid plans, GitHub sync carries no risk, and builds are enabled by default. CI compatibility matters just as much—because Depot and Buildkite execute existing GitHub Actions workflows, migration risk sits with the execution environment rather than with workflow definitions, which is welcome news where pipelines are long and numerous.
Bear in mind, though, that this is early beta. Enterprise organizations may opt out, and agent-native features are still coming. Repos under complex compliance, permissions, or audit obligations probably belong to a later stage. Builds also carry caveats, since they work via filesystem snapshots: extend your install command to cover everything that can be prepared in advance; use team or environment secrets for private registries, since user secrets stay out of builds and are injected when an agent starts; and remember that the start command still fires on your first prompt to an agent, so reserve it for services that must be fresh, such as Docker containers.
The Takeaway: A Stack Built Around Agents
Origin, Builds, and the SpaceX acquisition add up to one coherent strategy: once agents become the primary executors, every infrastructure layer around them has to be redesigned. Origin holds the code, Builds readies environments, SpaceX provides compute. For people building products or learning AI tooling, the lesson is plain—the next battleground is not better models alone, but the whole infrastructure that carries agent-driven development. Whether GitHub answers, and how, is the thing to watch; the race to redesign code hosting for agents has only just started.