December 19, 2025
Merge-mania meets comment chaos
Graphite Is Joining Cursor
Graphite joins Cursor, fans shout “hell yeah” while skeptics brace for merger vibes
TLDR: Graphite is being acquired by Cursor but will keep running while the two tools get integrated. Comments split between excitement and classic merger anxiety, with fans celebrating the combo and skeptics fearing product decay—plus jokes about finally escaping the pain of GitHub pull requests.
Graphite, the code review tool trusted by hundreds of thousands of engineers, is being acquired by Cursor—and the comments immediately turned into a live reality show. The official line: Graphite keeps operating independently while the two connect tools with smarter reviews and tighter bridges between writing code and reviewing it. Translation for non-devs: less hopping between apps, more seamless teamwork. Cue community reactions.
Cofounder Greg (aka fosterfriends) jumped in to explain the move, saying he wants to build bleeding‑edge tools with a team he loves—instant points for transparency. On the hype side, fans like saraverdi7 cheered, “two of my fave products under one roof,” while Hunter dropped confetti emojis and congrats. But the top spicy take belonged to timvdalen, who worried this is the classic “acquisition that ruins a good thing.” That skepticism hit a nerve: will beloved workflows stay intact?
Comedy hour arrived courtesy of baq, who begged to be freed from the “demon’s shackles from hell of GitHub PRs.” For the uninitiated, a PR is a pull request—basically asking teammates to approve your code changes (what’s a PR?). The vibe: half honeymoon, half doomscroll. If Cursor + Graphite actually tame PR chaos, the cheering section might win this one.
Key Points
- •Graphite has entered into a definitive agreement to be acquired by Cursor.
- •Graphite will continue to operate independently with the same team and product.
- •Graphite’s platform is used by hundreds of thousands of engineers at top organizations.
- •The companies plan tighter integrations between local development and pull requests.
- •Smarter code review features that learn from both systems are planned, alongside other new ideas.