SpaceXAI is looking to have a play in all parts of the AI stack.
Cursor, the coding tool that became part of Elon Musk’s empire after SpaceX closed its $60 billion acquisition of parent company Anysphere earlier this month, has announced a new product called Origin that puts it in direct competition with GitHub, the code hosting platform owned by Microsoft. Origin began rolling out on Monday in early beta to all paid Cursor plans, and it does something Cursor has never done before: host the actual code.
Until now, Cursor has been an editor that sits on top of wherever your code already lives, almost always GitHub. Developers write and review code inside Cursor, but the repository itself, along with the pull requests, the commit history, and the access controls, has always belonged to someone else’s infrastructure. Origin changes that arrangement. Cursor is now offering to be the place where the code actually sits, not just the tool used to write it.
What Origin actually does
The feature lives under a new Codebase tab inside Cursor. Users click “+New” to create a repository and give it a name, and Cursor responds with CLI instructions for cloning an existing repo or pushing a local project straight to Origin. The first repo a user creates also sets the name for their entire codebase, which becomes part of the URL structure going forward, so a company called Acme Corp would end up with repos addressable at cursor.com/codebase/acme-corp.
Every Origin repo comes with pull requests built in. Opening one surfaces the full timeline: commits, checks, files changed, and a diff view where reviewers can leave comments and merge directly. None of this is unfamiliar to anyone who has used GitHub, GitLab, or Bitbucket, and that appears to be intentional. Cursor isn’t trying to reinvent the pull request; it’s trying to own the environment where the pull request happens.
GitHub isn’t being pushed out, at least not yet
The more interesting part of the launch is how Origin treats existing GitHub repos. Rather than forcing a migration, Cursor lets users connect their GitHub account, pick an organization, and choose which repos to sync into Origin. Anyone with read or write access to a synced repo on GitHub automatically gets to view it in Cursor as well, and a repo can be disconnected at any point.
Synced repos update in real time, and browsing, searching, and pulling code all happen from the Origin copy. Pushes, however, still go back to GitHub, which Cursor is treating as the source of truth for any repo that started life there. Pull requests sync in both directions too: commenting inside Cursor posts the comment to GitHub, and reacting or replying on GitHub shows up back in Cursor within seconds. A review assigned on GitHub can be completed and merged entirely from within Cursor. Small icons next to each repo name indicate whether Cursor or GitHub is doing the hosting.
It’s a hedge that makes sense for a company entering this market from a position of having zero existing repos on its platform. Most teams are not going to rip their codebase off GitHub because a new tab appeared in their editor, so Cursor is starting by making itself useful as a layer over GitHub while quietly building the case for full migration over time.
Agents get access to the whole repo, not just the file open in the editor
Cursor is framing the bigger shift as agents having code, pull requests, and the ability to act on both in a single place. Inside a repo, users can ask Cursor questions about code they’re browsing, and the agent can answer, make changes, update existing pull requests, or push a new branch without leaving the page. The pitch is that an agent embedded at the hosting layer has more context than one that only sees whatever file happens to be open, and can act on an entire repository’s history and open PRs rather than a single working directory.
Building an app layer around Origin
Cursor is also opening Origin up to outside tools through what it’s calling app extensions, starting with Vercel, Depot, and Buildkite. Connecting Vercel from a repo’s Apps tab gives every pull request a preview deployment that can be tested and commented on before it merges to production. On the CI side, both Depot and Buildkite can run existing GitHub Actions workflows, and Buildkite additionally supports its own native pipelines. Cursor says more integrations are coming, an ecosystem play that mirrors what GitHub itself built around Actions and Marketplace over the past several years.
Every Origin repo also gets a settings page where teams can check GitHub sync status, manage access, and see which apps are connected to that particular repo.
The timing says a lot
Origin arrives roughly a month after Cursor became a part of Musk’s SpaceXAI division, the unit formed in February when SpaceX absorbed xAI. That deal, among the largest acquisitions of a venture-backed startup on record, turned Cursor’s four co-founders into billionaires practically overnight and gave the company access to SpaceX’s Colossus compute cluster. A code-hosting platform fits neatly into that broader ambition. Owning the editor gets you the coding workflow, owning the models gets you the intelligence layer, and owning the repository gets you the data and the distribution, all three feeding into an SpaceXAI stack that already includes Grok, Grok Build, and Grok Bot.
For Microsoft, the calculus is different. GitHub has sat largely unchallenged since Microsoft bought the company for $7.5 billion back in 2018, and its 150 million-plus users and deep integration with Copilot have made it the default home for source code across the industry. Origin is not going to dislodge that overnight, particularly with GitHub-first teams who see little reason to move a working setup. But Cursor already has a genuine foothold with developers who trust it for daily coding work, and asking those same developers to also host their repositories there is a far smaller leap than asking them to adopt an entirely new editor.
Origin is live in early beta across all paid Cursor plans starting this week, with enterprise organizations excluded only if their admins choose to opt out. Agent-native features specific to the hosting layer are described as coming soon, suggesting this week’s release is a foundation rather than the finished product.