Harvard study of 700+ firms finds AI coding agents raise code output but not software delivery, as code review time grows 49%
Harvard researchers Fiona Chen and James Stratton published a study using Jellyfish data (300M work events, 700,000+ employees, 700+ firms, 2021 to March 2026). After AI coding agents were introduced, lines of code rose 30%, commits 20% and pull requests 23%. Jira issue and epic resolution rates showed no statistically significant change. Review time rose 49%, the share of PRs with changes requested nearly doubled, comments per PR rose 35%, and the share of workers doing code review rose 14%. The study found no attributable employment changes. AI agents wrote 23.3% of review comments and covered 10.8% of PRs.
Entities: Fiona Chen, James Stratton, Harvard University, Jellyfish, Jira, GitHub
0 primary
What happened
Harvard researchers Fiona Chen and James Stratton analysed Jellyfish data covering 700+ firms and over 700,000 employees from 2021 to March 2026. After AI coding agents arrived, lines of code rose 30%, commits 20% and pull requests 23%. Jira issue and epic resolution rates showed no statistically significant change. Review time rose 49%, the share of pull requests with changes requested nearly doubled, and comments per pull request rose 35%. The study found no attributable employment changes. We only have this second-hand via Ars Technica, with no link to the paper, and it may not be peer-reviewed.
Why it matters
Engineering leaders get a concrete reason to measure delivery outcomes, such as issues resolved and time to ship, rather than code volume when judging AI coding tools. The findings suggest review capacity may be the constraint, so budgets and process changes may matter more than extra agent licences. The impact is still uncertain. The data comes from firms that use Jellyfish, and the study measures workflow proxies rather than product quality or revenue. Jira resolution is also a crude measure of delivered value.
What is noise
The headline claim that agents produce more code "but not more software" is stronger than a null result on Jira resolution rates supports, because "no significant change" is not proof of no benefit. The suggestion that deployment costs are not worth it for most companies is speculation, as the study did not measure costs or returns. More review comments and requested changes could reflect better scrutiny as well as worse code.
Watch next
- 01Publication of the actual paper or a preprint: check the difference-in-differences design, how agent adoption was dated, and whether it has been peer-reviewed.
- 02Replication or rebuttal using other datasets, such as GitHub, DORA-style delivery metrics, or vendor data, especially on cycle time and defect rates.
- 03Whether AI review tools reduce the 49% rise in review time, given agents already wrote 23.3% of review comments and covered 10.8% of pull requests.
Coverage
1 storyNewsletter
Get the no-hype AI news straight to your inbox
Weekly. No spam, unsubscribe any time. Privacy
More adoption signals
Full feed →- Meta releases Muse Spark Open, an open-weight ~816B-parameter multimodal mixture-of-experts model, with Hugging Face support15 Oct 202680
- Google DeepMind launches AlphaGenome Atlas, a free public database of predicted effects for 9 billion possible human genome variants8 Sept 202679
- Apple ships Gemini-powered Siri beta with iOS 27, excluding EU and China at launch15 Sept 202678
- Anthropic releases Claude Haiku 5.5 at sharply lower prices, halves Sonnet 5.5 cache read cost, and adds monthly API credits for subscribers7 Oct 202677