Cursor adds code hosting as GitHub's outage exposes platform dependence
Cursor opened its own repository layer while a seven-and-a-half-hour GitHub outage disrupted development worldwide and highlighted the two platforms' place in developer workflows.
Artificial Intelligence··Morning
Cursor brings repositories inside the product with Origin
Cursor, known for its AI code editor, opened a code-hosting layer called Origin to all paid plans in early beta on 17 August. The company's changelog says the first release covers repository creation, pull requests, code browsing and GitHub sync, with agent-specific features promised later. Repositories synced from GitHub work in both directions: a comment written in Cursor is posted to GitHub, and a reply on GitHub shows up in Cursor within seconds. Pushes still go to GitHub, which remains the source for anything started there. Integrations with Vercel, Depot and Buildkite are already available, and the rollout covers all paid users unless an enterprise admin opts out. The editor, review surface and repository sit inside one product, yet work that began on GitHub still treats that platform as its source of truth.[1]
GitHub broke for seven and a half hours, and Copilot fell with it
Microsoft's code-sharing platform GitHub, with 225 million users, broke at 06:40 Pacific on the morning of 17 August. According to GeekWire, the outage disrupted the website, code review and merge tools, the automated systems that test and ship software, and the Copilot coding assistant worldwide. GitHub found the source of the problem shortly after 09:30, had the outage under control by 10:00 and declared it resolved at 14:15, about seven and a half hours after it began. Scattered login failures affecting Copilot and other services continued through the afternoon, and the company said a detailed explanation would follow later. The platform has been straining under AI-driven coding for months: chief technology officer Vladimir Fedorov wrote in April that the company set out last autumn to grow capacity 10 times over, then concluded in February that it needed to build for 30 times its current scale.[2]
Sync continues while a single break point remains
In Origin's first release, pushes for repositories synced from GitHub still travel through GitHub, and comments written in Cursor appear on the other side within seconds. On the same day, GitHub's seven-and-a-half-hour outage took merge tools and Copilot down with it. The two developments arrive on separate channels: one is Cursor's product expansion, the other is the Microsoft platform's outage and capacity pressure. What they share is that much of daily coding work still hangs on the same hosting and review path. Origin opened in early beta on paid plans while login failures on the GitHub side stretched into the afternoon, making visible which layer of the developer workflow actually broke.[1], [2]
