by fosterfriends
8 subcomments
- Hi 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!
by bangaladore
19 subcomments
- Imo 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)
- If 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.
by timvdalen
5 subcomments
- I'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.
by outofdistro
0 subcomment
- How 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?
by scottydelta
0 subcomment
- > 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.
by ravirajx7
5 subcomments
- I’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.
- I 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.
by AbraKdabra
1 subcomments
- Startups should check the internet before naming them after tools like Graphite for monitoring https://graphiteapp.org/.
by spooky_action
6 subcomments
- Well, time to bite the bullet and learn jujutsu over the holidays
- if 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?
- Love 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.
- Congrats team! Graphite was basically what GitHub should have been but never was
Huge fans of their work @ GitStart!
by rileymichael
0 subcomment
- i mentioned a few months ago that it was a shame where graphite was headed re: AI (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
- I 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
by 2gremlin181
0 subcomment
- IMO 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.
- Blacksmith.sh acquisition in 3, 2, 1 ...
Then Cursor takes on GitHub for the control of the repo.
- 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
- 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?
- I guess this makes sense Github announced they are gonna bring stacked PRs this year so I think that kinda makes Graphite obsolute.
- 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.
- Does 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
by joecool1029
0 subcomment
- > 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...
- Confusing. I thought graphite was a TSDB
- 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.
by tomasreimers
4 subcomments
- Hi! Another one of the Graphite co-founders here. Alongside Greg, happy to answer any questions :)
by mcintyre1994
5 subcomments
- 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.
- If my company has an existing Cursor subscription, can we get Graphite for free?
- it 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?
by hunterbrooks
1 subcomments
- congrats Greg, Merrill, and the rest of the folks at Graphite!
- Hunter @ Ellipsis
by promiseofbeans
0 subcomment
- Oh, the code review system. I was worried that my favourite web svg editor got bought up: https://graphite.rs/
by saraverdi7
0 subcomment
- two of my fave products under one roof? ok hell yeah
by fractalnetworks
0 subcomment
- wtf is graphite and why do they assume everyone knows
- I thought it were graphite.art and had a figurative heart attack.
by eduardogarza
0 subcomment
- Such a common name honestly had no idea who it would be
by nextworddev
0 subcomment
- What? They could vibe code this?
- [flagged]
by starkiller
1 subcomments
- [flagged]
Hacker News