Cursor builds code hosting to escape Github dependency

Cursor isn't just adding a feature; it's signaling that AI-native tooling may no longer tolerate dependency on platforms built for human-first workflows. The real question is whether this succeeds because Github's terms are genuinely hostile to AI tools, or because Cursor is simply capturing switching costs while developers are already relearning their workflow.

This is largely disconnected from recent activity in the space, which has focused on model capability releases and safety research. What it does belong to is the emerging pattern of AI tool vendors building vertical stacks rather than integrating with incumbents. We haven't covered this consolidation trend directly yet, but it mirrors how mobile app ecosystems fragmented away from desktop platforms once the underlying compute model changed. The tension Cursor is exploiting (data access, training rights, revenue capture) is real, but whether it justifies full platform duplication remains unproven.

If Cursor's hosting platform captures more than 15% of its user base's repositories within 12 months, or if another major AI editor (like Windsurf or a new entrant) launches competing infrastructure within the next 18 months, that confirms this is a structural shift rather than a one-off bet. If Github responds by tightening AI tool access or raising API costs, that validates Cursor's thesis; if Github stays permissive, it suggests the fragmentation is optional rather than forced.