12 ms·
Graphite is joining Cursor
Graphite's announcement: https://graphite.com/blog/graphite-joins-cursor https://graphite.com/blog/graphite-joins-cursor
- fosterfriends 9mo agoHi all! Graphite cofounder Greg here - happy to help answer questions. To preempt one: I’ve been asked a few times so far why we decided to join. Personally, I work on Graphite for two reasons. 1) I love working with kind, smart, intense teammates. I want to be surrounded by folks who I look up to and who energize me. 2) I want to build bleeding-edge dev tools that move the whole industry forward. I have so much respect for all y’all across the world, and nothing makes me happier than getting to create better tooling for y’all to engineer with. Graphite is very much the combination of these two passions: human collaboration and dev tools. Joining Cursor accelerates both these goals. I get to work with the same team I love, a new bunch of wonderful people, and get to keep recruiting as fast as possible. I also get to keep shipping amazing code collaboration tooling to the industry - but now with more resourcing and expertise. We get to be more ambitious with our visions and timelines, and pull the future forward. I wouldn’t do this if I didn’t think the Cursor team weren’t standup people with high character and kindness. I wouldn’t do this if I thought it meant compromising our vision of building a better generation of code collaboration tooling. I wouldn’t do it if I thought it wouldn’t be insanely fun and exciting. But it seems to be all those things, so we’re plunging forward with excitement and open hearts!
- andsoitis 9mo agocongrats.
- jjmarr 9mo agoIf my company has an existing Cursor subscription, can we get Graphite for free?
- tomasreimers 9mo agoNot immediately - but I'm sure we'll find ways to bring the two products closer together over time :)
- momentsinabox 9mo agoReally appreciate the tone of this post. We need more leaders prioritizing words like love, kind, people, heart and character. Good on you. reply
- nadis 9mo agoMakes sense and appreciate the transparency. Have admired what you're building at Graphite and look forward to seeing what you build as part of the Cursor team. Congrats!
- barfoure 9mo ago> I wouldn’t do this if I didn’t think the Cursor team weren’t standup people with high character and kindness Somebody screenshot this please. We are looking at comedy gold in the next 3 years and there’s no shortage of material.
- julianozen 9mo agoCongrats!! I see this as two great companies joining forces in a crowded space where it is clear the whole is worth more than the sum of their parts. Best of luck on your journey
- bostonvaulter2 9mo agoAs someone who loves all the non-AI portions of Graphite (the CLI and the reviewer UI) should I be worried about this acquisition? Or will the CLI and Reviewer Ui continue to be be maintained and improved?
- jacobegold 9mo agoMaintained, improved, and integrated. With more resources than ever. We're building whole platform. That's a lot more than just AI.
- tombert 9mo agoForgive some ignorance, but we use Graphite at work, and I don't dislike it or anything, but I haven't really been able to see its appeal over just doing a PR within Github, at least if you exclude the AI stuff. What do you like about the non-AI parts? I mean it's a little convenient to be able to type `gt submit` in order to create the remote branch and the PR in one step, but it doesn't feel like anything that an alias couldn't do.
- tomasreimers 9mo agoNo concerns! The plan is to maintain and improve both
- sam_s 9mo agoCongrats, Greg! Sounds like you found a great fit, and I'm excited for you
- timvdalen 9mo agoI'm really used to my Graphite workflow and I can't imagine going without it anymore. An acquisition like this is normally not good news for the product.
- fosterfriends 9mo agoHeard on the worry, but I can confirm Graphite isn’t going anywhere. We're doubling down on building the best workflow, now with more resourcing than ever before!
- zeroonetwothree 9mo agoWe’ve heard this many times before with other acquisitions so don’t be upset if people are a bit skeptical.
- firloop 9mo agoSupermaven said the same thing when they were acquired by Cursor and then EOLed a year later. Honestly, it makes sense to me that Cursor would shut down products it acquires - I just dislike pretending that something else is happening.
- saraverdi7 9mo agorelax
- rozap 9mo ago"trust me bro" (6 months later) "An update about your graphite workspaces"
- trollbridge 9mo agoWe're aligning our product catalogue to do what we've found is the best fit for what our customers want. We're also excited to announce a migration plan to our new service, PencilLead, and want to offer existing customers preferential pricing to our Professional Services team to assist with the migration. We know this isn't what all of you want to hear, and we've spent the last year really evaluating this deeply. At the same time, we're glad you're part of our journey to the future of agentic AI and we think you'll find it's the best alignment and fit for you, too, long-term.
- baq 9mo agoif my employer has a cursor sub, but not a graphite sub, will this news free me from the demon's shackles from hell of github PRs?
- fosterfriends 9mo agoThis is my favorite question yet
- hunterbrooks 9mo agocongrats Greg, Merrill, and the rest of the folks at Graphite! - Hunter @ Ellipsis
- mlutsky1231 9mo agoThanks Hunter!
- saraverdi7 9mo agotwo of my fave products under one roof? ok hell yeah
- mcintyre1994 9mo agoThis 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 9mo agoYou 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 9mo agoExcept for the undismissable "Pay use more to enable AI reviews" nag that Graphite places above your CI checks and assigned reviewers.
- WXLCKNO 9mo agoNever 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?
- mcintyre1994 9mo agoThey 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.
- David 9mo agoNo, 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.
- raincole 9mo agoI thought it were graphite.art and had a figurative heart attack.
- seemaze 9mo agoNever used the tool being acquired, but just discovered the 2D design tool from your comment, looks super cool!
- tomasreimers 9mo agoHi! Another one of the Graphite co-founders here. Alongside Greg, happy to answer any questions :)
- Areibman 9mo agoWhat's the main synergy between Cursor and Graphite that led you to join? Stacked PRs? AI code review? Something else?
- babelfish 9mo agoStacked 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 9mo agoCongrats on the acquisition! I know its early but would existing cursor users get graphite for free/at a discount?
- fosterfriends 9mo agoIm sure we'll do something to simplify pricing and packaging in the future, but not right away
- elsigh 9mo agoCongratulations Tomas!
- acjohnson55 9mo agoAre 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.
- hzia 9mo agoCongrats team! Graphite was basically what GitHub should have been but never was Huge fans of their work @ GitStart!
- deleted 9mo ago[deleted]
- spooky_action 9mo agoWell, time to bite the bullet and learn jujutsu over the holidays
- wrs 9mo agoIt’s not so much biting the bullet as eating the delicious chocolate.
- MarcelOlsz 9mo agoThis is the comment that did it for me. I love chocolate. I'm in.
- _lvbh 9mo agoTook me a month to learn jujutsu. Was initially a skeptic but pulled through. Git was always easy to me. Its model somehow just clicks in my brain. So when I first switched to jj, it made a lot of easy things hard due to the lack of staging (which is often part of my workflow). But now I see the value & it really does make hard things easy. My commit history is much cleaner for one.
- Phlogistique 9mo agoWell, Graphite solves the problem of how to keep your stack of GitHub pull requests in sync while you squash merge the lowest pull request in the stack; which as far as I know jujutsu does not help with.
- dvtkrlbs 9mo agoI guess this makes sense Github announced they are gonna bring stacked PRs this year so I think that kinda makes Graphite obsolute.
- joshgachnang 9mo agoWoahhhhh I missed this. Got a reference or link? My Googling is failing me. That's my biggest complaint about Github coming from Gerrit for Open Stack.
- clayallsopp 9mo agonot op but I think from https://x.com/jaredpalmer/status/1980619222918262842 https://x.com/jaredpalmer/status/1980619222918262842
- dvtkrlbs 9mo agohttps://x.com/jaredpalmer/status/1999525369725215106?s=20 https://x.com/jaredpalmer/status/1999525369725215106?s=20 There is also a concept art (not sure if it is an actual prototype)
- dcre 9mo agoDo you have confidence they can execute?
- everfrustrated 9mo agoGitHub have proven the ability to execute very well when they _want_ to. Their product people are top notch. Given the VP of GitHub recently posted a screenshot of their new stacked diff concept on X, I'd be amazed if Graphite folks (whos product is adding this function) didn't get wind of it and look for a quick sell.
- dcre 9mo agoThis seems very very implausible to me as an explanation of what prompted them to get acquired. They wanted to get rich and stop having to fundraise!
- jjmarr 9mo agoIf my company has an existing Cursor subscription, can we get Graphite for free?
- starkiller 9mo ago[flagged]
- gravypod 9mo agoIf these ai companies had 100x dev output, why would you acquire a company? Why not just show screenshots to your agent and get it to implement everything? Is it market share? Because I don't know who has a bigger user base that cursor.
- dbgrman 9mo agoExisting users, distribution, and brand are a big part of acquisition. Graphite is used mainly by larger orgs. Also, graphite isn't just "screenshots"; it's a pretty complicated product.
- Bridged7756 9mo agoThe claims are clearly exaggerated or as you say, we'd have AI companies pumping out new AI focused IDEs left and right, crazy features, yet they all are Vs code forks that roughly do the same shit A VSCode fork with AI, like 10 other competitors doing the same, including Microsoft and Copilot, MCPs, Vs code limitations, IDEs catching up. What do these AI VsCode forks have going for them? Why would I use one?
- pizzafeelsright 9mo agoI am validating and testing these for the company and myself. Each has a personality with quirks and deficiencies. Sometimes the magic sauce is the prompting or at times it is the agentic undercurrent that changes the wave of code. More specific models with faster tools is the better shovel. We are not there yet.
- pizzafeelsright 9mo agoMy guess is the purchase captures the 'lessons learned' based upon production use and user feedback. What I do not understand is that if a high level staff with capacity can produce an 80% replacement why not assign the required staff to complete that last 10% to bring it to production readiness? That last 10% is unnecessary features and excess outside of the requirements.
- Angostura 9mo ago
- knes 9mo agoBlacksmith.sh acquisition in 3, 2, 1 ... Then Cursor takes on GitHub for the control of the repo.
- jacobegold 9mo agoAs a Graphite employee, would love this tbh - we love Blacksmith!
- gk1 9mo agoLove this announcement style. Direct, confident, and not a word longer than it needs to be. Gives major "the work speaks for itself" vibes. OpenAI's comms used to be like this, until it morphed into Apple-like grandiosity that instead comes off as try-hard.
- AbraKdabra 9mo agoStartups should check the internet before naming them after tools like Graphite for monitoring https://graphiteapp.org/ https://graphiteapp.org/.
- nozzlegear 9mo agoGraphite should check the dictionary before naming itself after a soft, black, lustrous form of carbon. https://www.merriam-webster.com/dictionary/graphite https://www.merriam-webster.com/dictionary/graphite
- AbraKdabra 9mo agoYeah well at least the OG graphite is not software.
- nozzlegear 9mo agoSure, but if the concern is googling "graphite" and finding results that aren't the Graphite you're looking for, it's the same problem. There will always be more results for graphite, the mineral than graphite, the enterprise-ready monitoring tool. If that's not the concern, then what's the big deal?
- AbstractH24 9mo agoThe number of tools with this name is shocking
- ravirajx7 9mo agoI’m working on something in a similar direction and would appreciate feedback from people who’ve built or operated this kind of thing at scale. The idea is to hook into Bitbucket PR webhooks so that whenever a PR is raised on any repo, Jenkins spins up an isolated job that acts as an automated code reviewer. That job would pull the base branch and the feature branch, compute the diff, and use that as input for an AI-based review step. The prompt would ask the reviewer to behave like a senior engineer or architect, follow common industry review standards, and return structured feedback - explicitly separating must-have issues from nice-to-have improvements. The output would be generated as markdown and posted back to the PR, either as a comment or some attached artifact, so it’s visible alongside human review. The intent isn’t to replace human reviewers, but to catch obvious issues early and reduce review load. What I’m unsure about is whether diff-only context is actually sufficient for meaningful reviews, or if this becomes misleading without deeper repo and architectural awareness. I’m also concerned about failure modes - for example, noisy or overconfident comments, review fatigue, or teams starting to trust automated feedback more than they should. If you’ve tried something like this with Bitbucket/Jenkins, or think this is fundamentally a bad idea, I’d really like to hear why. I’m especially interested in practical lessons.
- 0xedd 9mo agoWe have coding agents heavily coupled with many aspects of the company's RnD cycle. About 1k devs. Yes, you definitely need the project's context to have valuable generations. Different teams here have different context and model steering, according to their needs. For example, specific aspects of the company's architecture is supplied in the context. While much of the rest (architecture, codebases, internal docs, quarterly goals) are available as RAG. It can become noisy and create more needless review work. Also, only experts in their field find value in the generations. If a junior relies on it blindly, the result is subpar and doesn't work.
- abound 9mo agoAt $DAYJOB, there's an internal version of this, which I think just uses Claude Code (or similar) under the hood on a checked out copy of the PR. Then it can run `git diff` to get the diff, like you mentioned, but also query surrounding context, build stuff, run random stuff like `bazel query` to identify dependency chains, etc. They've put a ton of work into tuning it and it shows, the signal-to-noise ratio is excellent. I can't think of a single time it's left a comment on a PR that wasn't a legitimate issue.
- bangaladore 9mo agoImo Cursor did had the first mover advantage by making the first well known AI coding agent IDE. But I can't help but think they have no realistic path forward. As someone who is a huge IDE fan, I vastly prefer the experience from Codex CLI compared to having that built into my IDE, which I customize for my general purposes. The fact it's a fork of VSCode (or whatever) will make me never use it. I wonder if they bet wrong. But that's just usability and preference. When the SOTA model makers give out tokens for substantially less than public API cost, how in the world is Cursor going to stay competitive? The moat just isn't there (in fact I would argue its non-existent)
- archon810 9mo agoAs someone who uses Cursor, i don't understand why anyone would use CLI AI coding tools as opposed to tools integrated in the IDE. There's so much more flexibility and integration, I feel like I would be much less productive otherwise. And I say this as someone who is fluent in vim in the shell. Now, would I prefer to use vs code with an extension instead? Yes, in the perfect world. But Cursor makes a better, more cohesive overall product through their vertical integration, and I just did the jump (it's easy to migrate) and can't go back.
- deleted 9mo ago[deleted]
- mckn1ght 9mo agoMobile developer here. I historically am an emacs user so am used to living in a terminal shell. My current setup is a split pane terminal with one half running claude and the other running emacs for light editing and magit. I run one per task, managed by git worktrees, so I have a bunch of these terminals going simultaneously at any given time, with a bunch of fish/tmuxinator automation including custom claude commands. I pop over to Xcode if I need to dig further into something. I’ve tried picking up VSCode several times over the last 6-7 years but it never sticks for me, probably just preference for the tools I’m already used to. Xcode’s AI integration has not gone well so far. I like being able to choose the best tool for that, rather than a lower common denominator IDE+LLM combination.
- AlexB138 9mo agoI wonder about this. Graphite is a fantastic tool that I use every day. Cursor was an interesting IDE a year ago that I don't really see much of a use case for anymore. I know they've tried to add other features to diversify their business, and that's where Graphite fits in for them, but is this the best exit for Graphite? It seems like they could have gotten further on their own, instead of becoming a feature that Cursor bought to try to stay in the game.
- alexgotoi 9mo ago[flagged]
- scottydelta 9mo ago> We’re sunsetting Supermaven after our acquisition one year ago. > After bringing features of Supermaven to Cursor Tab, we now recommend any existing VS Code users to migrate to Cursor. Supermaven was acquired by Cursor and sunset after 1 year.
- deleted 9mo ago[deleted]
- 2gremlin181 9mo agoIMO this is a smart move. A lot of these next-gen dev tools are genuinely great, but the ecosystem is fragmented and the subscriptions add up quickly. If Cursor aquires a few more, like Warp or Linear, they can become a very compelling all-in-one dev platform.
- deleted 9mo ago[deleted]
- asdev 9mo agoDoes anyone get actual insightful reviews from these code review tools? From most people I've spoke with, it catches things like code complexity, linting, etc but nothing that actual relates to business logic because there's no way it could know about the business logic of the product
- epolanski 9mo agoI built an LLM that has access to documentation before doing code reviews and forces devs to update it with each pr. Needless to say, most see it as an annoyance not a benefit, me included. It's not like it's useless but... people tend to hate reviewing LLM output, especially on something like docs that requires proper review (nope, an article and a product are different, an order and a delivery note are as well, and those are the most obvious..). Code can be subpar or even gross but to the job, but docs cannot be subpar as they compound confusion. I've even built a glossary to make sure the correct terms are used and kinda forced, but LLMs getting 95% right are less useful than getting 0, as the 5% tends to be more difficult to spot and tends to compound inaccuracies over time. It's difficult, it really is, there's everything involved from behaviour to processes to human psychology to LLM instructing and tuning, those are difficult problems to solve unless your teams have budgets that allow you hiring a functional analyst that could double as a technical and business writer, and these figures are both rare and hard to sell to management. And then an LLM is hardly needed.
- hamdingers 9mo agoGraphite is a pull request management interface more than it is an AI code review tool.
- crabmusket 9mo agoI have gotten code reviews from OoenAI's Codex integration that do point out meaningful issues, including across files and using significant context from the rest of the app. Sometimes they are things I already know but was choosing to ignore for whatever reason. Sometimes it's like "I can see why you think this would be an issue, but actually it's not". But sometimes it's correct and I fix the issue. I just looked through a couple of PRs to find a concrete example. I found a PR review comment from Codex pointing out a genuine big where I was not handling a particular code path. I happened to know that no production data would trigger that code path as we had migrated away from it. It acted as a prompt to remove some dead code.
- promiseofbeans 9mo agoOh, the code review system. I was worried that my favourite web svg editor got bought up: https://graphite.rs/ https://graphite.rs/
- geoffbp 9mo agoConfusing. I thought graphite was a TSDB
- arthur-st 9mo agoThere 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 9mo ago> 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/142309/3 https://forum.cursor.com/t/font-on-the-website-looks-weird/1...
- mat_b 9mo agoGood 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.
- rileymichael 9mo agoi mentioned a few months ago that it was a shame where graphite was headed re: AI (https://news.ycombinator.com/item?id=44955187 https://news.ycombinator.com/item?id=44955187). this appears to be the final nail in the original products coffin for anyone else looking for a replacement, git spice and jujutsu are both fantastic
- storus 9mo agoWhy 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_ 9mo agoI don't experience this. I'm still able to choose models with meta+/
- eduardogarza 9mo agoSuch a common name honestly had no idea who it would be
- nextworddev 9mo agoWhat? They could vibe code this?
- 1317 9mo agoit would be nice if these tools named themselves something other than some random dictionary word, so you could tell what they are what does graphite have to do with code review?
- fractalnetworks 9mo agowtf is graphite and why do they assume everyone knows
- outofdistro 9mo agoHow does Graphite compare with other AI code review tools like Qodo? My team has been using Qodo for a while now and i've found it to be pretty helpful. EVery once in a while it finds a serious issue, but the most useful part from my experience are the features that are geared towards speeding up my review rather than replacing it. Things like effort labels that are automatically added to the pr and a generated walk through that takes you through all of the changed files. Would love to see a detailed comparison of the different options. Is there some kind of benchmark for AI code review that compares tools?
- nottorp 9mo agoSo 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?
- novoreorx 9mo agoI don't even know what Graphite is. I hope acquisition announcements like this assume the reader has no prior knowledge of what is being acquired
- matt3210 9mo agoThis 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
- AbstractH24 9mo agoIs this another acquisition for talent or will the product be kept and actively maintained?