Researchers examined real-world use of AI coding tools across hundreds of firms from 2021 to 2026 using Jellyfish data.
AI coding agents increase lines of code by about 30%, commits by about 20%, and pull requests by roughly 23%.
Despite more code, there is no significant rise in finished software features due to bottlenecks in code review and integration.
Quick read · 1 min
A new study tracks how AI coding tools are used in real teams. It finds AI agents boost lines of code, commits, and pull requests, but don’t automatically increase the amount of software that ships.
Why it matters: more code doesn’t equal faster or better software unless teams can accelerate reviews and integration.
What to watch for next: researchers want better metrics and guidance on turning AI-generated changes into finished features.
AI coding agents raise output but not finished software.
Code review bottlenecks limit gains.
Better review processes could unlock real productivity gains.
A new look at how AI coding tools are used in real teams finds a familiar pattern: more code gets written, but not more usable software ships. The study, led by Harvard University researchers Fiona Chen and James Stratton, shows that while AI coding agents can speed up writing code, they don’t automatically translate into more completed software. In plain terms: more code doesn’t necessarily mean faster or better products for users.
The researchers analyzed data from Jellyfish, a platform that tracks how engineering teams work. The data set spans 2021 through March 2026 and covers hundreds of firms, including millions of work events like commits and pull requests from hundreds of thousands of engineers. They compared teams that started using AI coding assistants (which suggest and complete human-authored code) and AI coding agents (which can generate and submit code autonomously) against teams that did not use these tools yet.
What they found: after AI agents are introduced, total lines of code rise by about 30 percent, commits increase by around 20 percent, and pull requests grow by roughly 23 percent. But the measure of actual software output, finished features and deliverables tracked in project management systems, did not show a meaningful improvement. In other words, more code does not automatically mean more features reaching users.
The authors emphasize a key constraint: the code review and integration process becomes a bottleneck that absorbs much of the potential gain from AI tooling. ReviewActivity and issue resolution did not shift in a statistically significant way after AI tools arrived, suggesting teams still need to complete the same heavy lifting before new code becomes part of a product.
01
Which tools and practices matter most?
The study distinguishes between AI coding assistants (which aid human authors) and AI coding agents (which can generate and submit code). The biggest uptick in output happens with agents, but this does not automatically translate into more shipped software, largely because downstream review and testing remain slow and manual.
If you rely on frequent software updates at work or on consumer apps, this study helps explain why you might not see faster feature rollouts even as development teams adopt AI tools. AI can produce more code, but the real value comes when teams streamline reviews, testing, and deployment so those changes can actually reach users.
03
What teams can do next
To turn AI-written code into real products, teams should focus on speeding up the review and integration steps. This could mean tighter governance on what AI-generated changes are allowed to submit, faster validation checks, and improved workflows that keep pull requests moving. In short, AI can crank out more code, but people must decide which changes matter and how they fit the roadmap.
04
What happens next
Researchers plan to refine measurement methods to better capture the downstream effects of AI in software pipelines and to explore how organization structure and incentives influence tool adoption. For readers, that means watching how teams implement review simplifications and QA processes alongside AI use.
No. The study finds more output in code, but no clear rise in finished software, underscoring the ongoing need for human review and decision making.
What should I look for if my team uses AI coding tools?
Watch how quickly code moves from authoring to review. If pull requests stall, teams may need faster reviews, better testing, and clearer feature scoping.
When will AI tools deliver real productivity gains?
Only when downstream bottlenecks, reviews, testing, and deployment, are improved along with AI usage.
OpenAI released hundreds of AI-generated math results across hundreds of papers, leaving researchers to sort truth from touting and decide what’s actually correct.
4 min read
We use cookies to understand how readers use Talk With Tech, so we can make it better. Is that OK? Privacy policy
The Daily Brief
Today's biggest tech stories, in 5 minutes
Every morning, the news that matters from AI, phones, apps and the people shaping tech. Explained in plain English. Free.
One email a day. No spam, unsubscribe anytime. Privacy policy