Cursor Origin launches with GitHub sync and AI coding tools

Cursor has begun an early-beta rollout of Origin, a code-hosting service that gives developers a way to host repositories and handle code reviews inside its AI editor. For teams considering Cursor Origin GitHub sync, the key detail is that existing GitHub repositories can remain anchored at GitHub while being viewed and worked on in Cursor.

Origin started rolling out on Aug. 17 to users on Cursor’s paid plans, according to the company’s changelog. Enterprise organizations can be excluded when their administrators opt out. The release extends Cursor beyond its editor into the systems developers use to store code, review changes and merge work.

How does Cursor Origin work with GitHub?

Users can connect a GitHub organization, choose individual repositories to synchronize and later disconnect them. For repositories that began on GitHub, GitHub remains the source of truth and pushes continue there, Cursor said. The Origin copy updates in real time and can be used to browse, search and pull code.

That arrangement gives developers a lower-commitment way to test Origin rather than requiring an immediate move of a team’s codebase. Pull-request activity also crosses between the services: comments made in Cursor post to GitHub, while GitHub reactions and replies appear in Cursor within seconds, according to Cursor. Developers can review and merge assigned GitHub pull requests from Cursor.

Code hosting is the service that stores a project’s code and manages the shared workflow around it. Origin’s initial features include hosted repositories, code browsing, pull requests, repository-access settings and command-line instructions for cloning repositories or pushing a local project, Cursor said.

What can Cursor’s AI agents do in Origin?

One distinction is that Cursor places code, pull requests and its AI agents in the same interface. Cursor says an agent can answer questions about code being viewed, make changes, update a pull request or push a branch. The company says further “agent-native” capabilities are planned, without detailing them in the launch announcement.

Origin also arrived with integrations for Vercel, Depot and Buildkite. Cursor says Vercel can create a preview deployment, a testable version of an application, for each pull request and send a merged change to production. Depot and Buildkite can run existing GitHub Actions workflows, while Buildkite also supports its own native pipelines.

Why did the launch draw attention?

The rollout coincided with a GitHub service degradation. VentureBeat, citing GitHub’s incident log, reported the disruption began about three and a half hours after Origin’s rollout and lasted six hours and 42 minutes. Error rates were near 20% for pull requests, issues and the API, the software interface used by other applications, and near 50% for archive and raw-file downloads.

The timing made Origin’s GitHub-compatible approach more visible, but does not establish that Cursor planned its release around the incident. VentureBeat reported that product releases are scheduled weeks ahead and said there was no evidence of such timing.

This story draws on original reporting from TechCrunch.