Agent PRs Surged From 4M to 17M in Six Months. The Bottleneck Moved.

The assumption most teams are operating on: AI coding tools help you write code faster, so you ship faster. paddo.dev documented why that assumption breaks down. Agent-authored pull requests have grown from 4 million to 17 million in six months. The code creation isn't the problem anymore. The problem is everything downstream.

"Creation runs at machine speed. Release engineering does not."

That line stuck with me. I've felt this in my own projects. I can spin up three Claude Code sessions and generate a week's worth of changes in an afternoon. But reviewing those changes, testing edge cases, resolving merge conflicts between agent-generated branches, and actually deploying? That still moves at human speed. I'm not bottlenecked on writing code. I'm bottlenecked on shipping it.

This is a structural shift, not a tooling gap. When your PR queue grows 4x in six months, the answer isn't "review faster." The answer is automating the merge-to-deploy pipeline. CI that understands agent-generated code patterns. Automated rollback triggers. Canary deployments that catch the subtle bugs agents introduce, the kind that pass unit tests but fail in production because the agent didn't have full context about how the system actually behaves under load.

The connection to story #4 below is direct: GitHub just published a guide specifically addressing how to review agent-generated PRs, because the review process itself needs rethinking. Over-abstraction, hallucinated dependencies, logic that technically works but misses the intent. These patterns don't show up in traditional code review checklists.

For solo builders like me, this is manageable. For teams? If you don't have automated CI/CD pipelines with good test coverage right now, you're about to drown in PRs that nobody has time to review properly.