HackerPapers

arXiv:2511.04427cs.SE

Speed at the Cost of Quality: How Cursor AI Increases Short-Term Velocity and Long-Term Complexity in Open-Source Projects

Hao He, Courtney Miller, Shyam Agarwal, Christian Kästner, Bogdan Vasilescu

Abstract

Large language models (LLMs) have demonstrated the promise to revolutionize the field of software engineering. Among other things, LLM agents are rapidly gaining momentum in software development, with practitioners reporting a multifold increase in productivity after adoption. Yet, empirical evidence is lacking around these claims. In this paper, we estimate the causal effect of adopting a widely popular LLM agent assistant, namely Cursor, on development velocity and software quality. The estimation is enabled by a state-of-the-art difference-in-differences design comparing Cursor-adopting GitHub projects with a matched control group of similar GitHub projects that do not use Cursor. We find that the adoption of Cursor leads to a statistically significant, large, but transient increase in project-level development velocity, along with a substantial and persistent increase in static analysis warnings and code complexity. Further panel generalized-method-of-moments estimation reveals that increases in static analysis warnings and code complexity are major factors driving long-term velocity slowdown. Our study identifies quality assurance as a major bottleneck for early Cursor adopters and calls for it to be a first-class citizen in the design of agentic AI coding tools and AI-driven workflows.

arXiv comments
Journal reference
23rd International Conference on Mining Software Repositories (MSR '26), April 13--14, 2026, Rio de Janeiro, Brazil
DOI
doi:10.1145/3793302.3793349
Subjects
cs.SESoftware Engineering cs.AIArtificial Intelligence

On Hacker News

Linked by 2 identifiable commenters in 2 comments across 2 threads, from Mar 2026 to Oct 2026. Found in 8 HN submissions from Nov 2025 to Mar 2026. Open submission discussions.

Comments linking this paper, per year.

Discussed in comments2 threads

    • A double-difference comparison between GitHub projects that have adopted Cursor and paired projects that have not: https://arxiv.org/abs/2511.04427 https://arxiv.org/abs/2507.09089

      ghboo0927View on HNParent context

    • You don't. This is the kind of problem created by vibe coding. Escalate upwards, challenge the policy, cite this as an example. Also cite things like https://arxiv.org/abs/2511.04427 : "transient increase in project-level development velocity, along with a substantial and…

      JoshTriplettView on HNParent context

Submitted to Hacker News

Connected through shared HN threads, not inferred similarity or a recommendation.