What Cursor Actually Shipped, and to Whom
On 17 August 2026, Anysphere, the company behind the Cursor AI code editor, rolled out Origin, a git-hosting and code-review platform, in early beta to every user on a paid Cursor plan. There was no separate opt-in: it turned on automatically, and an opt-out is available only to administrators on Enterprise plans. Origin gives teams a Codebase tab for hosting repositories, browsing and searching code, and running pull requests with bidirectional sync back to GitHub, plus pre-built integrations with Vercel for preview deployments and with Depot and Buildkite for CI pipelines.
Cursor is careful about what Origin is not. Its own description states: 'Pushes keep going to GitHub, which stays the source of truth for anything started there.' Origin is not pitched as a GitHub replacement - it is a second platform sitting alongside it, arriving two months after Cursor's December 2025 acquisition of the code-review startup Graphite, a deal that already signaled an ambition to own code review, not just code editing.
The Outage That Landed the Same Day
Hours before Origin's rollout, GitHub suffered a major global outage. The incident opened around 13:40 UTC on 17 August 2026 and affected Pull Requests, Issues, Actions, Webhooks and Copilot; general web and API traffic saw roughly 20 percent error rates, while archive downloads and raw repository content saw closer to 50 percent. Downdetector logged more than 3,000 reports worldwide, with regional peaks in the US and India.
GitHub's own status page marked seven of the eight affected services as mitigated by 16:59 UTC, restoring API Requests, Actions, Git Operations, Issues, Pages, Pull Requests and Webhooks to operational. Copilot was the exception, still listed as a major outage after the rest of the platform recovered. GitHub had not published a root cause by the time Origin's rollout was underway.
The Dependency Map Most Teams Have Not Updated
Most engineering teams' disaster-recovery plans treat GitHub as the single point of failure for source code, because until this week it effectively was. That assumption stopped being accurate on 17 August 2026: a second platform, from a different company, now holds a live sync of the same repositories and gives AI agents direct read and write access to them - and it turned on for most paid users without a decision being made by anyone at the company using it.
Neither Cursor's changelog nor its blog discloses an EU hosting region or data-residency option for Origin. For a codebase that is pure application logic, that is a business-continuity question. For any codebase that carries personal data in test fixtures, log samples or code comments - which most real repositories do somewhere - it is also a GDPR Article 28 question: a new processor with write access to that data just onboarded itself, and most data processing agreements were signed before it existed.
What to Check This Week
Start with the Cursor admin console. If your organization is not on an Enterprise plan, Origin is already live for your team; Enterprise admins should confirm whether they exercised the opt-out or inherited it silently. Then extend the incident-response runbook that currently reads 'if GitHub is down' to also cover 'if Origin is down' or 'if Cursor is down' - two outages in one supply chain are no longer a hypothetical after this week.
Finally, check the CI/CD side of the chain. Origin ships with pre-built integrations to Vercel, Depot and Buildkite; each is a US company, and each now sits in the same pipeline as your code. None of this requires panic - Origin genuinely solves a real problem for teams running fleets of AI coding agents. It does require an honest, current answer to a question that got harder to answer this week: how many vendors, in how many jurisdictions, can currently read your source code.
Read next: Grok Bot Signs Into Your Apps and Never Logs Off | Cursor's Cheapest Seat Runs a Different Model
