GET THE AUTOPSY ➔

AI now writes half of what goes into Linear. Teams tripled their pull requests. Linear itself says it has no idea if any of that helped.

The viral headline says AI made teams slower. Linear's actual report never measured shipping speed at all.

01THE CLAIM
"AI now writes just under half of all Linear issues, teams that connected a coding agent tripled their weekly pull requests — and total product development time increased anyway." [SOURCE ↗]
TRUE, BUT8 SOURCES · LIVE 2026-08-25
AITOOLSRECAP TRACK RECORD1 CLAIM · 40/100 BS RATE →
just under halfshare of everything created in Linear now written by AI (agents/MCP), vs fewer than 1 in 1,000 issues two years earlier
21 to 65weekly pull requests for teams that connected a coding agent, over two years (~3.1x)
8 to 10weekly pull requests over the same period for teams without a coding agent
+17%rise in engineering time spent on issue CREATE AND TRIAGE, June 2025 to June 2026 — the only 'time rose' metric in the report
zerocycle-time, time-to-merge, or time-to-production metrics reported by Linear
32.7%merge rate of AI-assisted pull requests, per LinearB's 8.1M-PR dataset
84%merge rate of unassisted/manual pull requests, same dataset
AI now writes half of what goes into Linear. Teams tripled their pull requests. Linear itself says it has no idea if any of that helped.
02THE CHECK

THE CLAIM. AI now writes just under half of everything created in Linear, teams with a coding agent tripled weekly pull requests from 21 to 65, and total product development time increased anyway.

THE CHECK. Linear's own data report backs the first two numbers, verbatim. The third doesn't exist in it. What actually rose is "time spent creating, triaging, and commenting," Linear's own words, for time logged inside the issue tracker, not time-to-ship. Linear has never published a cycle-time or time-to-merge number in this report.

THE TWIST. Linear says it plainly: "we have no way of knowing whether this increased output led to positive business outcomes." A separate dataset of 8.1 million pull requests found AI-assisted PRs merge at roughly half the rate of human-written ones, meaning tripled PR volume isn't tripled delivered work. Three more PRs a week and no faster ship date is not a contradiction. It's coordination overhead with better marketing.

03SAY THIS IN THE MEETING · 📸 SCREENSHOT IT
"Linear's own report says it can't tell if any of that extra output was worth anything. The "teams ship slower" headline is doing work Linear's data doesn't do."
04YOUR MOVE ⚡ WHAT IGNORING THIS COSTS

PR count and issue count are activity metrics, not delivery metrics. If your team's dashboard is bragging about AI-driven volume, ask what happened to cycle time before you believe the volume meant anything.

05🔮 OUR CALL · ON THE RECORD 2026-08-24

The next viral "AI slows teams down" story will trace back to the same move: a volume metric relabeled as a speed metric. Watch for it.

Flips if Linear or a comparable tracker publishes an actual cycle-time or time-to-production metric showing AI-adopting teams shipping slower, not just logging more activity.

RECEIPTS (8) · CONFIDENCE HIGH · every URL below answered a live HTTP check before publish · sweep 2026-08-25

  • linear.app · "Teams now use AI to write just under half of everything created in Linear"
  • linear.app · "Teams that connected a coding agent roughly tripled their weekly pull requests over two years, from 21 to 65"
  • linear.app · "Between June 2025 and June 2026, time spent creating, triaging, and commenting rose in nearly every function"
  • linear.app · "We have no way of knowing whether this increased output led to positive business outcomes"
  • aitoolsrecap.com · "Total product development time increased anyway."
  • web.archive.org · "AI prs merge at just 32.7%, which is less than half of that rate."
  • faros.ai · "Volume is up, quality is down, and the gap between the two is widening as adoption deepens."
  • web.archive.org · "manual PRS merge at about 80, 84 point half percent, so about 84% of all the unassisted prs that are open get merged"

This story is a stable, citable object. If you can falsify a verdict, tell us. Corrections are loud here.