Cursor Now Stores Your Code. Does That Matter to You?

TL;DR: On 17 August, Cursor launched Origin, its own code hosting service — and GitHub spent most of that same day broken. The timing is not subtle. For you, the honest answer is that nothing changes yet: Origin is an early beta, paid plans only, and GitHub stays the official home of anything that started there. But it’s worth two minutes to understand what code hosting is, because you almost certainly rely on it without having chosen it.

What happened

Cursor added Origin to its changelog on 17 August 2026. It does the things GitHub does: stores your repositories, shows you the code, handles pull requests with comments flowing both ways, and syncs with your existing GitHub repos. It plugs into deployment tools including Vercel, Depot and Buildkite.

It’s in early beta for all paid plans, at no extra cost. Free-tier users don’t get it, and enterprise administrators can opt their organisation out. Setting it up means creating a repo in the Codebase tab and installing a command-line tool — so it is, for now, aimed at people comfortable with a terminal.

The line that matters most is Cursor’s own: “Pushes keep going to GitHub, which stays the source of truth for anything started there.” This is not a replacement. It sits alongside.

Then there’s the timing. GitHub went down the same day. According to IT Pro, the outage ran from 13:40 to 21:15 UTC — about seven and a half hours — taking out the API, Actions, pull requests, issues, webhooks and Copilot, with roughly a 20% error rate on the web and API and around 50% on repository downloads. GitHub hasn’t said what caused it. TechCrunch counts 257 GitHub outages in the past year, and attributes the strain to the surge in AI-assisted coding traffic — which is, of course, partly Cursor’s own doing.

What code hosting actually is

If you’ve built anything with an AI tool, you’ve probably been asked to “connect your GitHub” and done it without knowing why. Here’s the plain version.

Your project is a folder of files. Code hosting is a website that keeps the master copy of that folder, remembers every change anyone made, and lets more than one person — or more than one AI agent — work on it without overwriting each other. GitHub is the one nearly everyone uses: roughly 180 million users, owned by Microsoft since 2012.

Think of it as Google Docs for a folder of code: the version history, the shared copy, and the “who changed what” trail. A repository is just one project’s folder living there.

That’s why an outage is more than an inconvenience. When code hosting is down, deployments stall and automated jobs fail. Your app that’s already live keeps running — but shipping a change to it doesn’t.

Why it matters if you don’t code

Three honest points, in descending order of usefulness.

1. Today, this changes nothing for you. Origin is a beta for paying Cursor users that needs a terminal, and GitHub remains the source of truth. If you weren’t already comfortable with the command line, this isn’t your moment.

2. The reason it exists is the interesting part. A 257-outage year, and a seven-hour failure on launch day, is a real problem that AI coding created. Every AI tool in the category leans on the same infrastructure. The question “what happens to my project when the thing underneath it falls over?” is now a fair one to ask of any tool you’re paying for.

3. It’s a lock-in question, and you should treat it as one. Cursor is now owned by SpaceX, and it would now like to hold your code as well as write it. That may be entirely fine. But we said the same thing yesterday about an automation tool that gave users a month to leave: the value of keeping your work portable only becomes obvious on the day you need it.

What to do

1. Nothing, if you’re on the free plan or you don’t use a terminal. You’re not eligible and you’re not missing out.
2. If you’re a paying Cursor user, you can try it without committing. GitHub sync means you can point Origin at an existing repo and keep GitHub as the master copy.
3. Don’t make Origin the only home for anything yet. It’s an early beta from a company that has been part of SpaceX for less than a week.
4. Do learn where your code actually lives. Open your tool’s settings and find out which account holds it. Most people building with AI genuinely don’t know, and it takes a minute.
5. Keep GitHub even if you like Origin. Free, universally understood, and the fallback everyone else can read.

Who should care (and who shouldn’t)

• Paying for Cursor and comfortable with a terminal: the only group who can use this today. Worth a look; keep GitHub in sync.
• Building a revenue app on Cursor: interesting, not urgent. Revisit when it leaves beta.
• Using Lovable, Bolt, Replit or Horizons: nothing to do — they handle code hosting for you, which is rather the point of them. Our comparison covers who does what.
• Learning, or not started yet: ignore this completely. The quiz is a far better 60 seconds.

Our take

We’d file this under “sensible strategy, not yet your problem”. Cursor has spotted a genuine weakness in a competitor and moved on it fast, and the outage on launch day made the argument better than any marketing could. That is a good business decision.

What we’d resist is the implied conclusion that you should now move your code into the tool that writes it. Concentration is convenient right up until it isn’t, and the last month has given us a shutdown, an acquisition and a seven-hour outage to think about. Use Origin if it’s useful. Keep the copy somewhere else.

Not sure which AI tool fits what you’re building? Take the 60-second Vibe Coding Tool Finder quiz →

Start free with Cursor → or see how it compares in our tool breakdown.

Some links on this page are affiliate links. If you buy through them we may earn a commission at no extra cost to you.

FAQ