What it means for leaders

Merge rates show how much agent work survives human review. A rate close to the baseline means agent output is treated like any contributor's; a much lower one means reviewers are spending time on work they reject.

What would change the reading: The gap between agent and all pull requests closing or widening.

The trend

June 30, 2025August 31, 2026

The breakdown

August 31, 2026.
  • Agent pull requests84.8%
  • All pull requests78.9%

Every reading

DateValueChangeSource
84.8%+1.5 pointsSource
83.3%+2.4 pointsSource
80.9%−2.6 pointsSource
83.5%+0.1 pointsSource
83.4%+3.6 pointsSource
79.8%+0.4 pointsSource
79.4%+4.3 pointsSource
75.1%−2.0 pointsSource
77.1%−0.7 pointsSource
77.8%−3.0 pointsSource
80.8%+1.1 pointsSource
79.7%−3.1 pointsSource
82.8%−0.9 pointsSource
83.7%−1.7 pointsSource
85.4%—Source

Definition and method

What it measures
Of the pull requests cloud coding agents opened in the month, the share merged by the end of the following month. Parts compare agent pull requests with all pull requests.
Population
Pull requests opened in public GitHub repositories
Updated
Monthly, one month behind

Caveats

  • Public repositories only.
  • Agents are identified by the app account that opens the pull request, or for OpenAI Codex by its "codex/" branches, which some people also use by hand; agent work submitted through a person's own account (most local coding assistants) is not counted.
  • Merged isn't the same as correct: some teams merge agent work and fix it later.

Cite this

Enterprise AI in Numbers, "Share of AI agent pull requests merged, versus all pull requests", https://lucianoayres.com/ai-brief/data/agent-pr-merge-rate/, retrieved October 25, 2026. Data: GitHub search API, our monthly counts.

Download every indicator (CSV) · Methodology