What Changed: Cursor Now Hosts Your Code
On August 17, 2026, Cursor announced a one-line changelog entry: “Cursor can now host your code.” That’s the arrival of Origin, a code hosting service in early beta for all paid plans. It’s a significant move: a company known for its AI-powered editor is now stepping into territory long dominated by GitHub. But Origin isn’t just another repository host. It’s designed from the ground up for agent scale—meaning the features prioritize how AI agents work with code, not just how humans do.
Origin launches with the essentials: repos, pull requests, code browsing, and GitHub sync. Agent-native features are promised soon. The key insight is that your code, PRs, and agents now live in the same interface. While browsing a repo, you can ask Cursor questions, make changes, update existing PRs, or push a new branch. For humans, that’s convenient. For agents, it’s a native operating environment—reading, reviewing, executing, and delivering no longer require hopping between three different systems.
This launch doesn’t happen in isolation. On August 13, Cursor introduced Builds to speed up cloud agent startup times. On August 14, Cursor announced it had officially been acquired by SpaceX, giving it access to the world’s largest GPU fleet. Together, these three pieces form a vertical stack: Origin handles where code lives, Builds prepares the execution environment, and SpaceX provides the compute. It’s a roadmap for vertically integrating the entire agent workflow.
How Origin Works: Repos, PRs, and the Codebase Tab
Origin introduces a new Codebase tab as the home for your Origin repos. To create a repo, you click +New, name it, and follow the instructions to install the CLI and push a local project. When you create your first repo, you also name your codebase, which becomes part of every repo’s URL—for example, cursor.com/codebase/acme-corp. This naming scheme hints at Cursor’s ambition: the codebase is a first-class concept, not just a list of repositories.
Pull requests are fully featured. Each repo has a PR view with timeline, commits, checks, and files changed. You can review diffs, leave comments, and merge directly from Cursor. For synced GitHub repos, PRs sync both ways: comments you make in Cursor post to GitHub, and reactions or replies on GitHub appear in Cursor within seconds. Reviews assigned to you on GitHub can be completed and merged from Cursor.
GitHub Sync: Zero-Migration Trial
The biggest concern for teams considering a new code host is migration: what happens to history, CI, permissions? Origin’s answer is a dual-track approach. You can connect your GitHub account, pick an org, and sync selected repos into Origin. These synced repos sit alongside Cursor-hosted ones, with icons indicating which is which. Synced repos update in real time—you browse, search, and pull from the copy in Origin, but pushes still go to GitHub, which remains the source of truth for anything started there. You can disconnect a repo at any time.
This design means you can try Origin with zero migration cost. Connect GitHub, see how agents perform with PR context, and decide later whether to start new projects directly in Origin. Cursor isn’t forcing anyone to choose sides—the competition happens at the experience layer, not the data layer.
App Extensions: CI and Previews
Origin also launches an app ecosystem. Integrations with Vercel, Depot, and Buildkite are already available, with more on the way. Connect Vercel from a repo’s Apps tab, and every PR gets a preview deployment where you can test and comment. Merge, and it ships to production. For CI, connect Depot or Buildkite—both run your existing GitHub Actions workflows, and Buildkite also supports its native pipelines.
This addresses another migration fear: having to redo your CI setup. Workflows are compatible; only the execution environment changes. For agent workflows, this is especially powerful: with preview deployments attached to every PR, every change an agent produces has a live environment for verification. Human reviewers see running results, not just diffs.
The Backdrop: Builds and the SpaceX Acquisition
Origin’s timing is tied to two other announcements. On August 13, Cursor introduced Builds—ready-to-use copies of your development environment prepared continuously in the background, at no extra cost. By default, Cursor runs a new build every hour. When you start an agent, it boots into a ready environment with repos cloned, dependencies installed, and the install script executed. This makes sessions start almost instantly, with responses up to 3x faster.
Builds also improve resilience. Cloud agents always start from the latest successful build. If a dependency bump breaks your install script or a Docker build fails, that build never becomes active, and you’re notified. New and existing sessions keep running safely while you debug in the background. You can inspect builds in the Cloud Agents dashboard, with logs and commit SHAs, and agents can manage builds via the Cursor Cloud MCP.
Cursor reports internal environments now boot 10x faster and time to first token is 3x faster. Customer Faire runs more than 2,000 automated agent runs per week, with their largest, most complex repos starting in seconds. As of August 17, all new and existing environments use builds by default, at no additional cost.
On August 14, Cursor announced it had officially been acquired by SpaceX, completing a process that began in April with a partnership with SpaceXAI. Cursor will have access to the world’s largest GPU fleet, enabling stronger models that are more economical to run. Grok 4.6, released August 12, is an early look at what they can build together.
Practical Implications and Limitations
If you’re already using Cursor cloud agents heavily, Origin is worth trying today: it’s on all paid plans, GitHub sync is risk-free, and builds are enabled by default. The CI compatibility with GitHub Actions via Depot and Buildkite means migration risk falls on execution environment, not workflow definitions—good news for teams with complex CI pipelines.
However, Origin is in early beta. Enterprise organizations can opt out, and agent-native features are still coming. If your repos have complex compliance, permissions, or audit requirements, this may not be the right stage for you. Also, builds work via filesystem snapshots, so there are caveats: update your install command to cover everything that can be prepared ahead of time; use team or environment secrets for private registries (user secrets stay out of builds and are injected at agent start); and the start command still runs when you first prompt an agent, so use it for services that must be fresh, like Docker containers.
Takeaway: The Agent-Native Stack
Origin, Builds, and the SpaceX acquisition form a coherent strategy: when agents become the primary executors, every layer of infrastructure must be redesigned around them. Origin manages code, Builds prepares environments, and SpaceX provides compute. For product builders and AI tool learners, the lesson is clear: the next competitive battleground isn’t just better models—it’s the entire infrastructure that supports agent-driven development. Watch how GitHub responds; the race to redesign code hosting for agents has just begun.
Sources
AI-assisted summary compiled from the sources above, reviewed by a human before publishing.