The Editor Now Owns the "Place You Keep Your Code" Too — Cursor Ships Its Own Hosting, "Origin," While GitHub Stays the Source of Truth

Cursor, a tool for writing code, has now built a place to keep it. On August 17, the company released Origin, an editor-integrated code hosting service, as an early beta for paid plans. It's an attempt to let you create repositories, handle pull requests, browse code, and run agent operations all in one place, without ever leaving the editor.

A "Shelf for Repositories" Inside the Editor

Origin lets you create repositories from a new "Codebase" tab. Each repository you create is assigned a URL in the form cursor.com/codebase/<name>, and you clone and push your local projects following the CLI's guidance. It's available on the Pro, Teams, and Enterprise paid plans; it isn't open to the free plan. On Enterprise, admins can disable it via opt-out.

What stands out is a design that doesn't replace GitHub but keeps it as the source of truth. When you sync an existing GitHub repository, a copy is updated in real time, and you can browse, search, and pull from the Origin side. Pushes still go to GitHub, though, so you can keep your source of truth on GitHub. It's a low-friction entry point you can try without switching over all at once.

Pull Requests and Agents Live on the Same Screen

What sets Origin apart from a mere storage locker is that review and automation are built in from the start. Its main features break down into three:

• Pull request management: Shows the timeline, commits, checks, and diffs, and syncs bidirectionally with GitHub. Comments can be written from either screen.
• Agent operations: Ask questions about the code you're viewing, request changes, update pull requests, and have it push branches — all from the same place.
• External service integrations: Vercel spins up a preview environment for each pull request, while Depot and Buildkite run your existing GitHub Actions workflows (Buildkite also supports its own pipelines).

Hosting, review, CI, and deployment — steps that are usually scattered across separate tabs — are consolidated onto a single surface that an agent can traverse. That's the crux of this move.

"Editing, Storage, Automation — All Under Our Roof": A Calculated Move

Until now, Cursor relied on a competitor — GitHub — for the place to keep code. With Origin, it pulls that dependency in-house and moves to vertically unify the flow of editor, hosting, and agent. From a developer's point of view, there's less tool-switching in the loop of opening a repo, reviewing it, and asking an agent to fix it. In an era of handing long-running work to agents, having that work's target — the code and PRs — under the same roof as your tools is no small advantage.

If you're weighing whether to adopt it, a realistic, incremental approach is to first sync an existing GitHub repository, keep GitHub as the source of truth, and try out Origin's pull request screen and agent operations. The preview and CI integrations cost less to set up the more your team is already using GitHub Actions.

A Few Caveats Lurking Behind the Convenience

That said, there are reasons it's hard to recommend without reservation. First is lock-in. The more you concentrate editing, storage, and automation in a single vendor, the heavier switching becomes — and the current design that lets you keep GitHub as the source of truth is, flipped around, also a state where "the migration isn't done."

Second is the question of who owns it. According to reports, Origin's release comes just days after SpaceX completed its roughly $60 billion acquisition of Cursor. Under whose control, and on what terms, is paid developers' code being stored? It's hard to say the data-handling terms were clearly spelled out at launch, and some caution that you'll want to check the terms of service and where your code lives before entrusting production code to it. Third, Origin is still in early beta: GitHub's surrounding features like issue tracking and self-hosting aren't there yet, and advanced conflict resolution and the like are reportedly slated for 2027 or later. It's a stage where you'll want to weigh what you're entrusting to a single vendor against the convenience you get in return.

References: Origin Code Hosting · Cursor Changelog / Cursor begins Origin code hosting rollout for paid plans (TestingCatalog) / Cursor launches Origin, a code hosting platform built for AI coding agents (Tech Startups) / Cursor Origin: agent-first git hosting and GitHub alternative (explainx.ai)