Anthropic blog Code Review (Last-Modified 2026-10-02) and docs: multi-agent Code Review research preview for Claude Code Team/Enterprise. Parallel find→verify→rank; overview + inline comments; never approves/blocks. Vendor stats: substantive comments 16%→54%; large PRs 84% with findings; ~$15–25/review, ~20 min. Local /code-review remains for other plans.

Key Takeaways

  • ✓Sources: claude.com/blog/code-review + code.claude.com docs; Last-Modified 2026-10-02
  • ✓Team/Enterprise research preview; not for ZDR orgs; others keep local /code-review
  • ✓Multi-agent find→verify→rank; CLAUDE.md/REVIEW.md; @claude review triggers
  • ✓Vendor: substantive comments 16%→54%; large PRs 84% with findings; ~$15–25/review
  • ✓Setup: GitHub App, per-repo triggers, spend caps; forks need explicit @claude review
🧭

Heavy Claude Code use: compare subscription limits and API bills

Compare 29+ dev plans & simulate token costs vs $20/mo subscriptions

🔬

In-Depth Technical Analysis

Background

Anthropic reports ~+200% code output per engineer YoY; review became the bottleneck. Code Review is the multi-agent system Anthropic runs on nearly every internal PR, now a research preview for Claude Code Team/Enterprise. Deeper (and costlier) than the open-source Claude Code GitHub Action; it never approves or blocks merges.

Mechanism

On PR open, parallel agents hunt bugs, a verification step filters false positives, findings are severity-ranked into an overview plus inline comments. Reviews scale with PR size (~20 min average). Docs: Important/Nit/Pre-existing; CLAUDE.md + REVIEW.md; @claude review / always / once; unavailable with Zero Data Retention; other plans keep local /code-review.

Benchmarks (vendor-reported)

Substantive review comments: 16% → 54% of PRs. Large PRs (>1000 LOC): 84% with findings, avg 7.5. Small (<50): ~31%, avg 0.5. <1% findings marked incorrect. ~$15–25 per review on tokens. Not a public SWE-bench score.

Playbook

Owner enables in Claude Code admin, installs GitHub App, picks per-repo triggers. Tune with REVIEW.md. Cap spend via org limits/analytics. Forks need an explicit @claude review. Prefer official blog + docs over secondary writeups.

Action HubReady to adopt this in production?

Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.