Graphite is joining Cursor

Posted by fosterfriends 12/19/2025

Graphite's announcement: https://graphite.com/blog/graphite-joins-cursor

276 points | 253 commentspage 3

geoffbp 12/19/2025|

Confusing. I thought graphite was a TSDB

arthur-st 12/19/2025|

There are two Graphite companies. The time series DB for metrics (not this) and the stacked diff code review platform (this). Looking at other comments under the post, they seem to have executed a hard AI pivot recently.

joecool1029 12/19/2025||

> The way developers write code looks different than it did a few years ago.

Looks bad: https://forum.cursor.com/t/font-on-the-website-looks-weird/1...

storus 12/19/2025||

Why doesn't Cursor allow selecting a LLM for code completion in the UI anymore and forces "auto" everywhere now? I have a Pro account and noticed this started like a month ago, and the "auto" output was often garbage, not following the instructions.

debo_ 12/19/2025|

I don't experience this. I'm still able to choose models with meta+/

nottorp 12/20/2025||

So is "company X is being bought by company Y" dirty language now?

Is corporate English becoming a form of newspeak and will significantly diverge from regular English over the next 100 years?

matt3210 12/20/2025||

This is an example of an AI project not working out and getting consumed by a higher wrung in the pyramid. Who will consume Anthropic later? Can’t wait to find out

mat_b 12/19/2025||

Good news. Been using Cursor heavily for over a year now (on the Ultra plan currently). Hope we get access to this as part of our existing subscriptions.

tomasreimers 12/19/2025||

Hi! Another one of the Graphite co-founders here. Alongside Greg, happy to answer any questions :)

acjohnson55 12/19/2025||

Are there thoughts on getting to something more like a "single window dev workflow"? The code editing and reviewing experiences are very disjoint, generally speaking.

My other question is whether stacked PRs are the endpoint of presenting changes or a waypoint to a bigger vision? I can't get past the idea that presenting changes as diffs in filesystem order is suboptimal, rather than as stories of what changed and why. Almost like literate programming.

fosterfriends 12/19/2025||

I really like all these ideas - very similar to what we discuss internally! We need to iterate our way there, but working with Cursor makes some of these visions much more possible

Areibman 12/19/2025|||

What's the main synergy between Cursor and Graphite that led you to join? Stacked PRs? AI code review? Something else?

babelfish 12/19/2025||

Stacked PRs are a really natural fit for vibe coding workflows, it helps turn illegible 10k+ line PRs into manageable chunks that you can review independently. (Not affiliated with Cursor or Graphite)

pm90 12/19/2025|||

Congrats on the acquisition! I know its early but would existing cursor users get graphite for free/at a discount?

fosterfriends 12/19/2025||

Im sure we'll do something to simplify pricing and packaging in the future, but not right away

elsigh 12/19/2025||

Congratulations Tomas!

mcintyre1994 12/19/2025|

This is annoying, Graphite's core feature of stacked PRs is really good despite all the AI things they've added around their review UI. I doubt we'll want to keep relying on that for very long now.

dbalatero 12/19/2025||

You can still think of AI as one facet of Graphite's product that you can use or not depending on your work style. Stacked PRs are still a core piece and not going anywhere :)

victorvation 12/19/2025||

Except for the undismissable "Pay use more to enable AI reviews" nag that Graphite places above your CI checks and assigned reviewers.

WXLCKNO 12/19/2025|||

Never heard of graphite before today. Were they built specifically for AI code reviews or it's a pivot / new feature from a company that started with something else?

David 12/19/2025|||

No, they've been doing "managing stacks of dependent pull requests" for a lot longer than AI code review. I've mostly been a happy user, they simplify a lot of the git pain of continually rebasing and the UI makes stacks much easier to work with than Github's own interface.

mcintyre1994 12/19/2025|||

They started as a better PR review tool, with the main feature that you can stack PRs that have dependencies on each other. It solves the problem of having PRs merging into other PR branches, or having notes not to merge something until another PR merges. Recently they became an AI code review tool, and just added a bunch of AI tools to the review UI, but you could just ignore it and the core functionality was still great.

jacobegold 12/19/2025|||

stacked prs will only get better from here :) we have an incredible amount of resources to keep improving that part of our product.

qudat 12/19/2025||

check out a range-diff approach using patchsets: https://pr.pico.sh

More comments...