Earlier quoted context omitted.
You can just use Cursor as a chat assistant if you want.
But then you're paying far more than just using Claude web which can be used for tasks other than coding.
Your company can be paying for it
Tracking Copilot vs. Codex vs. Cursor vs. Devin PR Performance
41–50 of 124 posts
Re: Tracking Copilot vs. Codex vs. Cursor vs. Devin PR Performance
#42Re: Tracking Copilot vs. Codex vs. Cursor vs. Devin PR Performance
#43It is also worth looking at the number of unique repositories for each agent, or the number of unique large repositories (e.g., by the threshold on the number of stars). Here is the report we can check:
https://play.clickhouse.com/play?user=play#V0lUSCByZXBvX3N0Y...
I've also added some less popular agents like jetbrains-junie, and added a link to a random pull request for each agent, so we can look at the example PRs.
Re: Tracking Copilot vs. Codex vs. Cursor vs. Devin PR Performance
#44Total PRs between Codex vs Cursor is 208K vs 705, this is an enormous difference in absolute PRs. Since cursor is very popular, how does their PRs is not even 1% of codex PRs?.
The happy path way of getting code out of Codex is a PR. This is emphatically not true for Cursor.
Re: Tracking Copilot vs. Codex vs. Cursor vs. Devin PR Performance
#45Total PRs between Codex vs Cursor is 208K vs 705, this is an enormous difference in absolute PRs. Since cursor is very popular, how does their PRs is not even 1% of codex PRs?.
I didn't even realize Cursor could make PRs. I thought most people would create PRs themselves once they were happy with a series of commits.
Re: Tracking Copilot vs. Codex vs. Cursor vs. Devin PR Performance
#46Total PRs between Codex vs Cursor is 208K vs 705, this is an enormous difference in absolute PRs. Since cursor is very popular, how does their PRs is not even 1% of codex PRs?.
The happy path way of getting code out of Codex is a PR. This is emphatically not true for Cursor.
Feels like a sort of pollution.
Re: Tracking Copilot vs. Codex vs. Cursor vs. Devin PR Performance
#47(Disclaimer: I work on coding agents at GitHub) This data is great, and it is exciting to see the rapid growth of autonomous coding agents across GitHub. One thing to keep in mind regarding merge rates is that each of these products creates the PR at a different phase of the work. So just tracking PR create to PR merge tells a different story for each product. In some cases, the work to iterate on the AI generated co…
This is a great point! But there's an important tradeoff here about human engineering time versus the "learning in the open" benefits; a PR discarded privately consumes no human engineering time, a fact that the humans involved might appreciate. How do you balance that tradeoff? Is there such a thing as a diff that's "too bad" to iterate on with a human?
I do agree there is a balance here, and that the ideal point in the spectrum is likely in between the two product experiences that are currently being offered here. There are a lot of benefits to using PRs for the review and iteration - familiar diff UX, great comment/review feedback mechanisms, ability to run CI, visibility and auth tracked natively within GitHub, etc. But Draft PRs are also a little too visible by default in GitHub today, and there are times when you want a shareable PR link that isn't showing up by default on the Pull Requests list in GitHub for your repo. (I frankly want this even for human-authored Draft PRs, but its even more compelling for agent authored PRs).
We are looking into paths where we can support this more personal/private kind of PR, which would provide the foundation within GitHub to support the best of both worlds here.
Re: Tracking Copilot vs. Codex vs. Cursor vs. Devin PR Performance
#48It's hard to attribute PR merge rate with higher tool quality here. Another likely reason is level of complexity of task. Just looking at the first PR I saw from the github search for codex PRs, it was this one-line change that any tool, even years ago, could have easily accomplished: https://github.com/maruyamamasaya/yasukaribike/pull/20/files
Re: Tracking Copilot vs. Codex vs. Cursor vs. Devin PR Performance
#49yeah, GitHub Copilot PRs are unusable. from personal experience
Re: Tracking Copilot vs. Codex vs. Cursor vs. Devin PR Performance
#50Where is Claude Code? Surprised to see it completely left out of this analysis.