Who Finishes the Job? A Study of Follow-Up Fixes and Commit Authorship on AI Coding Agent Pull Requests
Source
Wannita Takerngsaksiri, Nhat Duong, Scott Barnett
Author
Wannita Takerngsaksiri, Nhat Duong, Scott Barnett
Date
Key takeaways · AI-distilled
Merged AI agentAn AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.Full definition → PRs drew verified follow-up fixes at 1.62 times the odds of merged human PRs from the same repositories over the same period, per the authors.
The agents mostly repair their own work: 69.6% of verified fixes to agent merges came from the same agent, and 76.4% of verified fix PRs were agent-authored across all their commits.
Candidate fixes were checked by human annotators plus an LLMA large language model — the neural network behind tools like Claude and ChatGPT, trained on huge amounts of text to predict what comes next.Full definition → judge whose agreement with humans (Cohen's kappa 0.78) roughly matched human-to-human agreement (0.77), with 90% direct-fix precision.
The sample comes from the AIDev-pop dataset, limited to open-source repositories with at least 500 stars, so findings may not carry over to private or smaller codebases.
Terms in this piece · Glossary
AI agent — An AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.
LLM — A large language model — the neural network behind tools like Claude and ChatGPT, trained on huge amounts of text to predict what comes next.
Why it matters
Directly quantifies post-merge maintenance burden across the major coding agents, useful evidence for teams deciding how much review agent PRs actually need.