Is GitHub Becoming Infrastructure While AI IDEs Own the Workflow?

Cursor’s acquisition of Graphite looks, at first glance, like just another AI dev-tools consolidation. But the real impact of this move isn’t about better code generation or faster reviews, but a strategically well-planned move to acquire and reshape the developer workflow.

Let’s dive deep into this and unpack how it could challenge the long-held dominant position of GitHub.

Cursor plans to integrate Graphite’s tech with its own AI coding tools, creating a more unified development experience from writing code to reviewing and merging it.

And as the CEO of Cursor puts it, the acquisition addresses a bottleneck in software development. “We focused on the writing side of things. Graphite has focused on the review side of things. We think the two together can make something even better.”

Together, the leadership at Cursor and Graphite want to build an end-to-end platform.

Graphite CEO Merrit Lutsky explains, “Cursor has defined the new way to write code, and we’re defining how you review and merge it. Putting those together lets you build an end-to-end platform.” 

This move comes at a time when the AI coding market is rapidly expanding amid intensifying competition from players like OpenAI, Anthropic, and GitHub Copilot.

While Lutsky has said this move is not meant to directly compete with the largest players, a closer look suggests this collaboration is a strategic bet on where developer workflows are actually heading.

Let’s decode how. 

What does this acquisition mean for developers?

1. Towards an End-to-End AI Development Loop: Cursor is no longer just a code writer, but by integrating Graphite, it’s moving towards an AI code generation and code review & quality checks, with better integration with real developer workflows like pull requests.

2. Smooth collaboration: Graphite’s support for stacked diffs/PRs is a big deal for teams- Smaller, dependent changes that don’t block work, reduced merge conflicts, and faster feedback loops.

3. Dev Tools Are Consolidating: This acquisition reflects a trend: AI coding tools are consolidating vertically. Teams want full-stack AI solutions, not just isolated capabilities.

In short, Cursor helps you code faster, and Graphite helps the team review and ship faster. And together they are trying to challenge the predominance of GitHub. 

A Challenge to GitHub

1. Change in usage: GitHub won’t lose users but might lose mindshare and workflow ownership. That's a downgrade in strategic control. If you write code, review changes, and prepare merges inside Cursor, GitHub is no longer where work happens. It becomes where work is stored. GitHub ends up becoming the final checkpoint, not the workspace.

2. Control is shifting from platform to environment: Control is moving to where developers actually spend their time. As review happens inside the IDE, pull requests become a later step, and GitHub mostly handles syncing and permissions while real decisions are made inside Cursor.

3. Workflow changes: Copilot enhances existing workflows by sitting on top of GitHub, while Cursor goes further by replacing the workflow and positioning itself as the primary interface for developers.

4. Code review has become part of the IDE: With Cursor integrating with Graphite, review feedback will happen while you’re writing code.  

5. GitHub allows workflow doesn’t enforces them: Graphite changes behavior by guiding developers to make smaller, sequenced changes by default. GitHub is flexible by design. It gives you tools, but it doesn't tell you how you must use them. It doesn't push you strongly in one direction. That's what allowing workflows means.

6. The decision-making shifts: Copilot helps you write code faster, but it doesn't decide how work should be broken up, reviewed, or shipped. Cursor combined with Graphite influences decisions, not just typing. That moves intelligence upstream, closer to the editor, and away from GitHub's web interface.

Will developers stop using GitHub? No.

What does this mean for GitHub?

GitHub is still the system of record. But its role may quietly change from being the center of development to being the backend infrastructure. 

Teams will still use GitHub, but they will spend less time thinking in GitHub terms. That's the risk. Not loss of users, but loss of control over the developer workflow. 

So yes, developers will continue doing everything in GitHub. But if better tools make work feel faster and cleaner outside GitHub, habits shift naturally. 

Platforms don't lose relevance overnight they lose it when they stop being where decisions are made. That's the long-term implication of this collaboration.

Conclusion:

As IDEs are gaining momentum, the real bottleneck has shifted to review, merge, and decision-making, and Graphite directly addresses that gap. For Cursor, this is a logical attempt to own more of the workflow inside the IDE. 

That is why the move feels quietly threatening to GitHub. GitHub can support similar workflows, but it largely enables them rather than enforcing or shaping them, which means decisions increasingly happen elsewhere.

At the same time, this acquisition lands at a sensitive moment for Cursor. Pricing changes and plan limits have created skepticism among developers.

But Cursor’s move also raises the bar for other AI IDEs. Standalone code review tools are increasingly at risk. As review shifts from a separate step to something embedded directly into AI-driven IDE workflows, tools limited to PR comments, analytics, or static checks will struggle to stay relevant unless they deeply integrate.

And it will be interesting to see whether Graphite will continue to evolve with the same focus, or whether it becomes absorbed or repurposed. If Cursor invests deeply and keeps Graphite opinionated and strong, this collaboration could meaningfully shift where developers review, decide, and ship code. 

If this sparked your curiosity, subscribe to our newsletter for the latest insights and updates.