GitHub Has a New Problem Called Cursor Origin

Cursor has entered the code-hosting market with Origin, putting it on a collision course with GitHub as AI agents change how developers write, review, and ship software.

The rise of coding agents is increasing the load on Git infrastructure, with more code, pull requests, and CI runs. Traditional code hosts like GitHub and GitLab are seeing unprecedented levels of traffic and are unable to handle this workload.

In fact, GitHub recently suffered a major outage that affected its website, API, pull requests, actions, webhooks, and Copilot. The outage continued for several hours, disrupting development workflows globally as AI-assisted coding traffic overwhelmed the service.

Cursor has now built its own Git storage system called Continuity (Cnt). Instead of relying on individual servers as the source of truth, Continuity stores a write-ahead log in S3-compatible object storage. Local Git repositories essentially act as warm caches.

Origin began rolling out in early beta on August 17—the same day as the GitHub incident—to users on Cursor’s paid plans. The platform lets developers host repositories, manage pull requests, browse code, and connect GitHub repositories. Cursor said more agent-native features are coming.

Vaibhav Sisinty, Founder of edtech startup GrowthSchool, believes Cursor’s new code hosting platform could give developers an alternative by bringing repositories, pull requests, code reviews, and deployments into the same environment as its AI coding tools. 

“Cursor is no longer an AI code editor. It’s becoming the full developer platform,” he remarked on X.

Abhishek Harshvardhan Mishra, Founder of AI research firm Deus Experiments, tells AIM that Origin is strongly Cursor-native. “If GitHub’s reliability issues persist, I believe Origin could emerge as a threat, allowing Cursor to gradually take market share from GitHub,” he says.

What is Origin?

Origin is built around Cursor’s existing AI coding workflow. Developers can create a repository from Origin’s new Codebase tab and push an existing local project using the Cursor CLI. Cursor then hosts the code on its platform.

The platform also supports GitHub repositories. Developers can connect a GitHub organisation, select repositories, and sync them to Origin. Changes to synced repositories are updated in real-time, while GitHub remains the source of truth for repositories that originated there.

Uros Miric, a tech YouTube creator with channel OrcDev, who tested Origin after its launch, said the platform is still in the early stages but found its GitHub integration smooth. “It’s still pretty raw. You can definitely see it’s a beta; a bunch of things are still missing in the UI and UX,” he said in the review.

Miric said syncing existing GitHub repositories to Origin was straightforward. He identified Origin’s automation features as the most interesting part of the platform. Developers can set automations based on repository events or schedules, allowing AI agents to automatically work on specific tasks. 

“You can configure all of that directly in Origin. I think that’s pretty cool,” Miric said. “We need something like GitHub, but built for the agentic era.”

Origin also brings pull request management into Cursor. Developers can view commits, check and change files, review diffs, leave comments, and merge pull requests. For synced GitHub repositories, comments and reactions made on either platform are reflected on the other.

Cursor is also integrating its coding agents directly into repositories. Developers can ask questions about the code they are browsing, request changes, update pull requests, or push a branch.

In February, Cursor said 30% of the pull requests it merges internally were being created by agents operating autonomously in cloud sandboxes. These agents run in isolated virtual machines, where they can build and test software before submitting pull requests for developers to review. 

Mishra notes that Cursor’s Bugbot, code review, and agent capabilities are superior to what GitHub offers through its Copilot package. He believes that, along with comparable pricing, can compel developers to move to Origin.

Origin also includes integrations with Vercel, Depot, and Buildkite. Vercel can create preview deployments for pull requests, while Depot and Buildkite can run existing GitHub Actions workflows. Buildkite also supports its native pipelines.

The move puts code hosting, repository management, and AI coding agents within the same platform. Cursor said it is building an app ecosystem around Origin, with more integrations planned, reducing the need for developers to switch between other development tools.

“The agent-native design of Origin is the first real leap beyond the bolted-on experience we’ve had with conventional GitHub + Copilot, and that difference is already enough to justify serious experimentation,” Himanshu Dubey, Co-founder of applied research and product lab Physera AI, notes.

He believes the current GitHub and Copilot combination still leaves room for improvement. “There are currently dozens of devtool companies that operate in the same IDE and GitHub layer and have been able to address developer pain points better than Copilot,” he says.

Dubey believes Origin can have an edge through its interface. On GitHub, developers typically open a pull request, review the diff, leave comments, and then switch contexts to ask Copilot or another agent about the same code. Origin brings these steps into the same interface. 

“The agent lives next to the code you’re browsing. It can answer questions about it, propose changes, update the PR, and push a branch without leaving the same interface,” he explains.

However, Deepak Kumar, a Bengaluru-based founder building the AI tools marketplace ToolJunction, believes Origin needs to offer a super AI-native experience that even captures the non-tech builders market. “New developers might shift to Origin, but it’s very hard for pre Claude/Codex era developers to switch to Origin,” he says.

GitHub Remains King

Origin’s biggest challenge is not repository hosting itself. GitHub has spent years building a developer platform around repositories.

GitHub combines source control with issues, pull requests, actions, security tools, package management, and a large ecosystem of third-party integrations. It also has a large installed base across open-source projects and enterprises.

That makes switching more complicated than moving source code from one Git host to another. Developers would also have to consider workflows, permissions, integrations, CI systems, and existing team practices.

Kumar says GitHub has a mature developer community. “I think more non-tech developers and builders who are just building with tools like Cursor, Replit, and Codex will use Origin. GitHub is about 20 years old, and we definitely cannot expect people to shift to another platform overnight,” he observes.

He would also not move his projects from GitHub to Cursor because of the former’s more mature community and his 10-year history of commits, graphs, and contributions. “GitHub is not just a code versioning storage tool; it's like a public profile for me as a resume.”

Kumar says he may consider using Origin for Cursor-related and side projects, but does not see himself moving his main projects away from GitHub. He points to GitHub’s free offering for individual developers as a key reason. 

“If GitHub decides to charge individual developers, then I might think about using Origin,” Kumar says.

Similarly, Dubey says organisations already have years of process and compliance built around GitHub. “Origin already has solid early integrations (Vercel, Depot, Buildkite) and can run existing GitHub Actions workflows through those partners, but that is still a thin slice compared with the depth and breadth of what teams rely on daily,” he says.

Dubey quips that the GitHub outage on launch day was ‘memetic’, yet the platform recovered and remains the default for most professional work. For him to seriously consider moving his projects, Cursor would need to close the gap in everyday reliability and completeness. “I think this is going to be the future, given that Origin is still in early beta for now,” he says.

Dubey says that in a world where agents are generating more commits and reviews, Origin’s continuous interface feels like the natural next step.

“Privacy and security matter, and nobody wants to discover later that agent activity or repository data has created unexpected exposure. I think human-in-the-loop is still required because there are critical actions to take,” he notes.

Cursor says it is not simply building another Git host. It is rethinking the storage architecture behind Git hosting to support large monorepos and the growing number of repositories created by AI agents.

For Origin, the challenge will be to prove that it can match the reliability, security, and ecosystem that large development teams expect from their primary code host.