Understanding Accepted AI Lines vs. All Merged Lines in the AI Tool Adoption report

Last updated: October 27, 2026

"Accepted AI Lines vs. All Merged Lines (Organization)" on the Tool utilization page compares the AI-generated lines your developers accepted, as each tool reports them, with the lines your organization merged in the same period.

Why it matters

It shows the scale and trend of AI use against total engineering output: whether accepted AI volume is growing faster than merged code, keeping pace, or stalling. It is a volume comparison, not attribution. It doesn't tell you which lines in a pull request AI wrote; for that, use AI code ratio on the Comparison report, which comes from agent traces.

How it works

Accepted AI Lines ÷ All Merged Lines

Accepted AI Lines is the volume of AI-generated code developers accepted, according to each tool:

  • Lines added from accepted AI suggestions.

  • Lines deleted from accepted AI suggestions.

  • Accepted Cursor tab completions, counted as 2 lines each.

  • For agents Span recognizes from pull requests (Devin, Codegen, Codex Cloud, Async Copilot), the lines in the agent's pull request.

  • Where agent traces cover a person and day, the trace data replaces the tool's own numbers.

Only people marked as code contributors whose tool accounts match their Span person count.

All Merged Lines is lines added plus lines removed in pull requests merged in the period, authored by code contributors. Ignored files, repositories, and branches (Settings → Metrics) are excluded.

Filter behavior

  • The chart always covers the whole organization. People and team filters at the top of the page don't change it, which is why its title ends in "(Organization)".

  • The tool selector changes only the accepted lines. Merged lines always cover every merged line, so a single tool's percentage is smaller than the all-tools percentage.

  • For a team or person view, select one tool. The breakdown grid then adds an "Accepted AI Lines vs. All Merged Lines" column by team or person, and that column does respect grouping.

Setup

  1. Open AI Effectiveness → AI insights → Tool utilization.

  2. Choose all tools or one tool in the tool selector.

  3. Find the Accepted AI Lines vs. All Merged Lines (Organization) chart.

  4. For per-team or per-person values, select one tool and scroll to the breakdown grid.

Things to know

  • It can exceed 100%. Developers accept AI code on branches that are squashed, rebased, or never merged, and rewrite or delete code before merging. Deletions count too. The grid's help text says it: "The percentage might be inflated due to developers using AI in development branches."

  • The two sides come from different systems. Nothing links a specific accepted line to a specific merged line.

  • It runs higher than AI code ratio. AI code ratio scores the merged code itself. Don't expect the two numbers to match.

  • Cursor runs higher than tools that report lines directly, because of the 2-lines-per-tab assumption.

  • Worked example. In March your developers accepted 9,000 Cursor lines and 3,000 Copilot lines, and the organization merged 10,000 lines. With all tools selected the chart reads 12,000 ÷ 10,000 = 120%. With Copilot selected it reads 3,000 ÷ 10,000 = 30%, because merged lines stay at 10,000.

Related articles

AI Tool Adoption Report

What is the definition of Accepted AI lines and why might it exceed 100%?

Understanding differences between AI Impact (Comparison), Tool Utilization, and Agent Traces

Understanding Agent Traces in Span (auspex)

GitHub Copilot Integration Guide

Need help?

Contact your Span account team or reach out to support@span.app.