From Industry Claims to Empirical Reality: An Empirical Study of Code Review Agents in Pull Requests
On the map: LLM agents and tool use → Software engineering coding agents
Abstract (arXiv)
Autonomous coding agents are generating code at an unprecedented scale, with OpenAI Codex alone creating over 400,000 pull requests (PRs) in two months. As agentic PR volumes increase, code review agents (CRAs) have become routine gatekeepers in development workflows. Industry reports claim that CRAs can manage 80% of PRs in open source repositories without human involvement. As a result, understanding the effectiveness of CRA reviews is crucial for maintaining developmental workflows and preventing wasted effort on abandoned pull requests. However, empirical evidence on how CRA feedback quality affects PR outcomes remains limited. The goal of this paper is to help researchers and practitioners understand when and how CRAs influence PR merge success by empirically analyzing reviewer composition and the signal quality of CRA-generated comments. From AIDev's 19,450 PRs, we analyze 3,109 unique PRs in the commented review state, comparing human-only versus CRA-only reviews. We examine 98 closed CRA-only PRs to assess whether low signal-to-noise ratios contribute to abandonment. CRA-only PRs achieve a 45.20% merge rate, 23.17 percentage points lower than human-only PRs (68.37%), with significantly higher abandonment. Our signal-to-noise analysis reveals that 60.2% of closed CRA-only PRs fall into the 0-30% signal range, and 12 of 13 CRAs exhibit average signal ratios below 60%, indicating substantial noise in automated review feedback. These findings suggest that CRAs without human oversight often generate low-signal feedback associated with higher abandonment. For practitioners, our results indicate that CRAs should augment rather than replace human reviewers and that human involvement remains critical for effective and actionable code review.
Key facts. Cited by 4 papers in the map (data through 14 Oct 2026). Placed in Software engineering coding agents, one of 16 directions in LLM agents and tool use. First posted on arXiv 3 Apr 2026.
Builds on
No reference list yet.
Built on by
Citing papers per year: 2026: 4.
4 papers.
- 2026All Smoke, No Alarm: Oracle Signals in Agent-Authored Test Codecited by 1
- 2026Augmentation with Dilution: A Large-Scale Empirical Study of Human Contributor Ecosystems After AI Coding Agent Adoptioncited by 0
- 20263100 Opinions on Code Review in an AI World: Building Causal Theory from Practitioner Discoursecited by 0
- 2026OpenCodeReview: Determinism over Non-Determinism for Cost-Effective Agent-Based Code Reviewcited by 0
- 2026OpenCodeReview: Determinism over Non-Determinism for Cost-Effective Agent-Based Code Review10 Aug 2026
- 20263100 Opinions on Code Review in an AI World: Building Causal Theory from Practitioner Discourse8 Jul 2026
- 2026Augmentation with Dilution: A Large-Scale Empirical Study of Human Contributor Ecosystems After AI Coding Agent Adoption24 Jun 2026
- 2026All Smoke, No Alarm: Oracle Signals in Agent-Authored Test Code16 Jun 2026
Similar, not cited
Close in wording, no citation either way
- 2026Not All Agents Are Equal: Code Quality and Post-Merge Maintenance Across Five Autonomous Coding Agents in the Wild
- 2026On the Footprints of Reviewer Bots Feedback on Agentic Pull Requests in OSS GitHub Repositories
- 2026AI-to-AI Code Reviews of GitHub Pull Requests
- 2026When AI Teammates Meet Code Review: Collaboration Signals Shaping the Integration of Agent-Authored Pull Requests
- 2026Investigating Autonomous Agent Contributions in the Wild: Activity Patterns and Code Change over Time
- 2026Why Are Agentic Pull Requests Merged or Rejected? An Empirical Study
- 2026These Aren't the Reviews You're Looking For How Humans Review AI-Generated Pull Requests
- 2026Where Do AI Coding Agents Fail? An Empirical Study of Failed Agentic Pull Requests in GitHub