Martin Monperrus does not hedge. In a paper posted to arXiv on June 11, “The End of Code Review: Coding Agents Supersede Human Inspection” argues that “every stated goal of code review can be served by agents at lower cost and higher throughput,” and that the hybrid setup most teams have settled into — agents write the code, humans remain the mandatory reviewers — “is a dead end” once the sheer volume of AI-generated output is taken seriously. It is a title built to travel, and it has: the paper generated a substantial round of debate among developers on Hacker News within days of posting, the kind of reaction that tends to follow claims which are either obviously true or usefully wrong. This one looks like the latter.
What the data actually says
The most direct test of Monperrus’s claim is not philosophical, it is empirical, and it does not cooperate with the thesis. In its “State of AI vs Human Code Generation Report,” published in December 2025, CodeRabbit analyzed 470 open-source GitHub pull requests — 320 AI-coauthored, 150 human-only — and found that AI-authored PRs averaged 10.83 flagged issues against 6.45 for human-only ones, roughly 1.7 times more overall. The gap widens where it matters most: critical and major findings ran 1.4 to 1.7 times higher in AI-coauthored code, logic and correctness issues were 75% more common, and security vulnerabilities showed up as much as 2.74 times more often. If agents genuinely superseded human inspection at every goal review is meant to serve, this is exactly the dataset that should not exist. Instead it describes a population of pull requests that needs more scrutiny, not less, precisely because an agent wrote a larger share of the code.
None of this means Monperrus is wrong about everything, and that is the more useful way to read the disagreement. The paper is on solid ground when it describes what has genuinely changed: an ensemble of agents can now read a diff line by line, cross-reference it against a codebase, flag inconsistencies, and do so on every single commit rather than on the subset a human reviewer has time for. What it gets wrong is treating that mechanical checkpoint as synonymous with review itself.
Reading a diff for bugs is a bounded, mechanical task, and mechanical tasks are exactly what agents are built to absorb.
The reviewer’s job was never just reading diffs
That distinction is the core of critic Blake Crosley’s response, published on his blog on June 24 under the title “Agents Supersede the Reviewer, Not the Review.” Crosley concedes the empirical point almost entirely before making the sharper one:
“Agents have superseded the reviewer: the human who reads a diff line by line looking for defects is doing a job an ensemble of agents now does better and on every commit. But the paper conflates that role with the review itself.”
The argument is not that human judgment survives inside the old checkpoint — it is that the checkpoint was never where the irreducibly human work actually lived. Reading a diff for bugs is a bounded, mechanical task, and mechanical tasks are exactly what agents are built to absorb. Deciding what the code is supposed to do in the first place, and who answers for it when the decision turns out to be wrong, are not mechanical tasks. They do not disappear when the diff-reading step is automated; according to Crosley’s framing, they relocate — upstream into the specification of intent, and downstream into accountability for outcomes, both of which remain stubbornly human because both involve consequences that fall on people, not systems.
A rhetorical overreach with a real shift underneath it
Put the two pieces of evidence side by side and a more precise picture emerges than either headline claim allows. CodeRabbit’s numbers show that AI-coauthored code is not yet trustworthy enough to waive inspection, which undercuts the strong version of Monperrus’s argument that review as a quality gate is obsolete. Crosley’s rebuttal shows why that inspection increasingly looks less like a human squinting at a diff and more like a human deciding, earlier, what “correct” was supposed to mean, and later, whether to stand behind what shipped. “The end of code review” is a headline that mistakes the automation of one narrow, mechanical checkpoint for the disappearance of judgment itself. What is actually underway — where in the pipeline human accountability sits, and how specification work absorbs the scrutiny that line-by-line reading used to provide — is a harder, less quotable story, and the one worth following instead.
