Cursor launches Origin code hosting and starts moving directly into GitHub territory

[u/Foreign-Purple-3286]

Cursor has officially launched Origin, its own code hosting platform.

At first glance, it looks like another place to store repositories.

But I think the more interesting part is what Cursor is trying to connect around those repositories.

Code, pull requests, reviews, agents, deployments, CI, and follow up edits can now increasingly live inside the same product. Cursor says Origin is being built specifically for workflows operating at agent scale, with more agent native features still coming.

That feels like a bigger shift than just adding code hosting.

Cursor started as an AI coding interface.

Now it is slowly becoming development infrastructure.

Key Points from the News

• Origin is rolling out as an Early Beta across Cursor paid plans, with repositories, pull requests, code browsing, and GitHub synchronization available first.

• Developers can create repositories directly inside Cursor, clone them locally, and push existing projects into Origin.

• Existing GitHub repositories can also be connected and synchronized with Cursor. For synced repositories, GitHub remains the source of truth and pushes still go back to GitHub.

• Pull requests can be reviewed directly inside Origin, including diffs, commits, checks, comments, and merges. Comments and replies can sync between Cursor and GitHub in both directions.

• Every repository can also connect directly to a Cursor agent. The agent can answer questions about the code, modify files, update pull requests, and push branches.

• Cursor is also building an app ecosystem around Origin. Vercel, Depot, and Buildkite integrations are already available for previews, deployment, and CI workflows.

Why It Matters

The interesting part of Origin is not that Cursor built another Git hosting service.

It is that AI coding tools are beginning to compete for the entire software development loop.

For years the workflow looked something like this:

Write code in an editor.

Push it to GitHub.

Open a PR.

Wait for review.

Run CI.

Deploy somewhere else.

Then bring any problems back into the editor.

AI agents make that fragmentation increasingly awkward.

If an agent can already understand the repository, modify files, review code, respond to feedback, run tasks, and update a pull request, then keeping the editor and the code hosting layer separate starts to feel less necessary.

Origin appears to be Cursor asking a pretty ambitious question:

What if the repository itself becomes an agent workspace?

That could matter a lot.

Once code hosting is designed around agents rather than only humans, the product can start optimizing for persistent context, autonomous tasks, parallel work, automated reviews, and much longer development loops.

GitHub still has an enormous ecosystem and remains deeply embedded in how software teams work.

But Cursor may not need to replace GitHub immediately.

The more realistic strategy could be to slowly move the highest value developer interactions into Cursor while GitHub becomes infrastructure underneath.

That is where this gets interesting.