“Findings get verified by other agents before humans review them. Several agents look for bugs at the same time. Then a separate group votes on each finding, and it only gets posted if enough of them agree it's real. Findings that are only about style, diagnostics, or cleanup get dropped. We A/B tested those filters on our own PRs before keeping them.”
AnthropicPublished by the organization itself (post), no named author
Anthropic sells AI or agent tools or services, so it has a reason to publish flattering numbers about AI. The passage stays in the archive; read it with that in mind.
How this was checked
Checked against the source by a first reader, then confirmed independently by a second reader who fetched the source without seeing the first reader's notes (Independent review agent (Claude Sonnet), blind second pass from passage text and citation only, no repository access, 2026-11-07).
Under '2. AI review on every pull request': 'Findings get verified by other agents before humans review them. Several agents look for bugs at the same time. Then a separate group votes on each finding, and it only gets posted if enough of them agree it's real. Findings that are only about style, diagnostics, or cleanup get dropped. We A/B tested those filters on our own PRs before keeping them.' Exact match.
How to cite this passage
Anthropic, “How the Claude Code team does code review”, claude.dev Blog (Anthropic), 2026-10-15, at Layer by layer: 2. AI review on every pull request. https://claude.dev/blog/solving-code-review-at-anthropic/ Archived at https://the-ai-record.com/passages/anthropic-separate-agents-vote-on-each-review-finding-2026
AnthropicPublished by the organization itself (post), no named author
Context. From the section on human approval, where the post sets three risk tiers for changes to Claude Code's repos, needing no, one or two human approvals.
AnthropicPublished by the organization itself (post), no named author
Context. "Those numbers" are the revert and incident rates: the sentence before says noticing a bad merge still depends on the author, on-call, and the revert and incident dashboards.
AnthropicPublished by the organization itself (post), no named author
Context. The two cuts drop three items from the post's list of what people stay responsible for: deciding whether to build a change, reviewing architecture that sets a pattern others will copy, and reading the evidence the checks produce.
AnthropicPublished by the organization itself (post), no named author
Context. The text description of a chart in the post comparing internal pull requests before and after changes to re-review, which the post lists as a cap of three rounds, re-reviewing only the new diff after the first few passes, flagging the class of bug, and not repeating findings already posted.
Post: How the Claude Code team does code review, claude.dev Blog (Anthropic), October 15, 2026, at How we make the reviewer better: Figure D, Review that converges (the chart's text description).
78% prs pass after one review round, internal pull requests, after the convergence changes (0.65 before). Level not stated
1.5% prs needing five plus review rounds, internal pull requests, after the convergence changes (0.089 before). Level not stated
1.32 iterations per PR avg review iterations, internal pull requests, after the convergence changes (2.08 before). Level not stated
Checked against the source[ Grade B ]Said in the last yearAnthropic: $47 billion revenue, run-rate, May 2026Sells AI toolsPassage page
AnthropicPublished by the organization itself (post), no named author
Context. About Code Review for Claude Code, Anthropic's AI pull-request reviewer, which the post says is now generally available on its Team and Enterprise plans.