Cursor just walked into GitHub’s house. The AI coding company launched Cursor Origin on August 17, in the changelog post, a code-hosting platform with repositories, pull requests, code browsing, and GitHub sync. It’s in early beta on all paid plans, and “agent-native features ship soon.”
That last line is the whole story. Every AI coding tool on the market is racing to ship agents that clone, branch, and merge without a human babysitting them. The missing piece has always been the host. GitHub was built for humans clicking through a web UI. Cursor Origin is the first serious attempt at hosting built for the machines doing the work.
I’ve been tracking this shift in my best AI coding agents guide, and this is the most concrete sign yet that the dev tool stack is being rebuilt around agents.
What Cursor Origin actually ships
The official changelog is unusually concrete for a beta launch. A new Codebase tab hosts your repos at a cursor.com/codebase/ URL. You create repos with a CLI, push local projects, and browse everything in one place.
Pull requests exist on every repo, with timelines, commits, checks, and diffs. You can review, comment, and merge without leaving Cursor. Agents live in the same place: ask a question about code you’re browsing, and the agent can answer, make changes, update PRs, or push a branch.
The part that makes this a genuine rival rather than a walled garden is sync. “Your GitHub repos can sit alongside the ones Cursor hosts,” Cursor says in the changelog.
“Connect GitHub to Cursor, pick your org, and you’ll see the repos you can sync. Select one and Cursor pulls it in.”
Sync is bidirectional for pull requests. Comment in Cursor and it posts to GitHub. React or reply on GitHub and it shows up in Cursor within seconds. Pushes to synced repos keep going to GitHub, which stays the source of truth for anything started there. You choose what gets synced and can disconnect any repo at any time.
There’s an app ecosystem forming already. Vercel, Depot, and Buildkite integrations are live inside Cursor Origin, and connect Vercel and every PR gets a preview deployment. Connect Depot or Buildkite for CI that runs your existing GitHub Actions workflows.
Availability is the catch. Origin is rolling out to all paid plan users starting August 17, except enterprise orgs whose admins opt out. Free-plan users are locked out entirely for now. Cursor hasn’t announced separate Origin pricing, so it’s bundled with whatever paid plan you already have.
Why now: GitHub keeps dropping the ball
The timing isn’t an accident. As TechCrunch reported, the platform “has struggled with widely reported outages and performance degradation and, as it drops the ball, Cursor is waiting to pick it up.”
On the same day Cursor launched Origin, GitHub suffered a lengthy worldwide outage: over six hours of degraded service with a nearly 20% error rate worldwide.
That’s not a one-off. TechCrunch cites a LeadDev analysis counting 257 GitHub outages over the past year, and “a visible exodus of high-profile users.”
Some 180 million developers use GitHub as of last October, per GitHub’s own metrics, and it remains the largest source-code host in the world. Nobody abandons that overnight. But every outage window is a sales pitch for the alternative, and Cursor is the first AI-native company with the audacity to make it.
The agent-native endgame
Most coverage is underselling this. Repos and pull requests are table stakes. The changelog’s one-liner about what’s next, “agent-native features ship soon,” is the actual product.
Look at the trajectory. Cursor already runs cloud agents that build, test, and ship code while you do other things. Its environments now boot 10x faster with cached builds, according to the same changelog. Now the company controls the hosting layer too: the repo, the CI, the preview deploys, and the agent runtime under one roof.
When hosting is designed for agents first, the review workflow stops being a web page you visit and becomes a stream you monitor. Your code, PRs, and agents in the same place is how the changelog puts it. That’s a fair preview of where all dev tooling is headed.
This is also the first big strategic move since SpaceX closed its $60 billion acquisition of Cursor earlier this month. The pattern since then reads like a consolidation play: SpaceXAI rebranded the AI arm, then open-sourced Grok Build and reset usage limits. Picking a fight with Microsoft-owned GitHub is less a side bet and more the main line.
What to actually do with this
If you’re on a paid plan, open the new Codebase tab and kick the tires. Sync one low-stakes GitHub repo, run a pull request through it, and see how the two-way comment sync feels. You’re not migrating anything. GitHub remains the source of truth for synced repos.
If you’re GitHub-only and happy, nothing here forces a move. But the first credible agent-native host now exists, and the next AI coding tool you adopt may expect it. The infrastructure layer under dev work is being rebuilt for agents, and the editor you use every day just became the platform too.
I don’t know if Cursor Origin beats GitHub. A decade of network effects doesn’t evaporate, and GitHub’s scale gives it a moat most startups would kill for. But for the first time in years, there’s a real choice, and it arrives exactly when reliability complaints have made developers willing to look.
