Cursor Origin Launches: A Git Forge Built for AI Agent Fleets - on the Day GitHub Went Down
Cursor Origin puts repository hosting, PR review, and agent orchestration under one roof. Early beta is live on all paid plans. Pricing and migration tooling are still not published.
Timed. Cursor Origin launched August 17 - a git forge built for teams of AI agents pushing code in parallel - on the same day GitHub suffered a global outage with 20% error rates across its API and web traffic. Cursor Origin is now in early beta on all paid plans. Four days after SpaceX closed its $60 billion Cursor acquisition, Cursor's first major product launch is a direct play for GitHub's repository hosting layer.
Takeaways
- Cursor Origin launches August 17 in early beta on all paid Cursor plans - a git forge for AI agent fleets
- Led by Tomas Reimers, co-founder of Graphite - acquired by Cursor in December 2025 for review and merge tooling
- Demo throughput: 22.6 commits per second in a single repo - no published benchmark methodology
- Git-compatible: standard history and branches are portable - PR discussions, CI configs, and integrations are host-specific
- Pricing, security architecture, data handling, and migration tooling not yet disclosed
Origin is a git forge - the layer around Git that stores repositories, manages pull requests, handles permissions, runs checks, and merges code. Git stays the underlying version control. What Origin replaces is the GitHub or GitLab layer above it. Standard Git history, branches, and tags can move between compatible hosts. Pull request discussions, issue trackers, CI configurations, and application integrations are host-specific - which means any serious evaluation of Cursor Origin depends on migration tooling and identity controls that Cursor has not yet published.
Tomas Reimers leads Origin inside Cursor. Reimers co-founded Graphite, a code-review tool originally built as an internal tool before turning into a product. Cursor acquired Graphite in December 2025 after identifying review and safe merging as the next bottleneck created by faster code generation. CEO Michael Truell introduced Origin at Cursor's Compile conference in June, pitching it as infrastructure for repositories receiving code from dozens of agents running in parallel - not individual developers committing one branch at a time. Cursor had initially targeted fall 2026 for Origin and delayed a planned August 11 launch before shipping on August 17.
Origin lands at the top of a stack Cursor has assembled throughout 2026. Cloud agents run autonomously in dedicated virtual machines. Firetiger, acquired earlier this month, monitors production deployments for regressions and feeds findings back into the coding agent loop. Bugbot reviews pull requests automatically. Automations trigger agent workflows from GitHub, Linear, Slack, and PagerDuty events. Cursor Origin is where code from all of those agents gets stored, reviewed, and merged - the repository layer Cursor did not previously own.
What Cursor has not published: Origin's pricing, its security architecture, its data-handling terms, and its tools for migrating repositories away from GitHub. Truell has said that 35% of pull requests merged inside Cursor internally come from agents running autonomously - which explains why Cursor built the hosting layer before most teams need it, but does not answer whether Origin's review controls and operational guarantees can hold production codebases. Throughput demos measure ingest speed. What engineering teams actually need to know is whether Cursor Origin can be trusted as a system of record.