Beyond Code Generation: Reliability, Verification, and Cost Economics in the Agentic Software Development Lifecycle
On the map: LLM agents and tool use → Software engineering coding agents
Abstract (arXiv)
AI coding systems are moving from autocomplete and chat toward agents that can inspect repositories, edit multiple files, run tools, write tests, open pull requests, and work for long periods with limited supervision. This capability changes the bottleneck in software delivery. Recent field studies show meaningful gains in coding activity, but newer evidence also shows that those gains attenuate sharply between writing code and shipping reliable software. Review, integration, testing, security, deployment, and production operations remain constraining stages, while the economics are shifting from predictable per-seat licensing toward variable token, tool, sandbox, CI, and rework costs. This paper synthesizes peer-reviewed software-engineering research, university studies, benchmark audits, production reports from major technology companies, developer telemetry, and cost-management evidence released primarily from 2024 through September 2026. No new model experiment is claimed; numerical findings remain attributed to their original studies. The synthesis proposes four engineering concepts: the Agentic SDLC Throughput Paradox, Production-Qualified Change (PQC), the Verification Tax, and an Agentic SDLC Control Plane that allocates autonomy subject to cost, reliability, and human-attention budgets. An evidence-based horizon then maps today's supervised agents to future policy-bounded software factories. The central research question shifts from how much code an agent can generate to how much production-qualified value an engineering system can deliver per dollar, per reviewer-hour, and per unit of operational risk.
Key facts. Cited by 1 paper in the map (data through 14 Oct 2026). Placed in Software engineering coding agents, one of 16 directions in LLM agents and tool use. Builds on 17 of its 43 references that are in the map. First posted on arXiv 4 Sep 2026.
Builds on
17 of 43 references.
Closest ancestors · 8
Same direction, newest first
- 2026Engineering Reliable Coding Agents: Evaluating and Operating the System Around the Model14 Aug
- 2026The Best Programming Language for Tokenmaxxing: An Investigation of Coding Agent Behavior Across Programming Languages24 Jul
- 2026Position: Coding Benchmarks Are Misaligned with Agentic Software Engineering16 Jun
- 2026Agentic AI in the Software Development Lifecycle: Architecture, Empirical Evidence, and the Reshaping of Software Engineering29 Apr
- 2026SWE-chat: Coding Agent Interactions From Real Users in the Wild22 Apr
- 2026Rethinking the Value of Agent-Generated Tests for LLM-Based Software Engineering Agents8 Feb
- 2025Why AI Agents Still Need You: Findings from Developer-Agent Collaborations in the Wild14 Jun
- 2024SWE-agent: Agent-Computer Interfaces Enable Automated Software Engineering6 May
Other references · 9
- 2023SWE-bench: Can Language Models Resolve Real-World GitHub Issues?cited by 3,373
- 2025Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivitycited by 101
- 2024Automated Unit Test Improvement using Large Language Models at Metacited by 75
- 2026CooperBench: Why Coding Agents Cannot be Your Teammates Yetcited by 23
- 2026SWE-Marathon: Can Agents Autonomously Complete Ultra-Long-Horizon Software Work?cited by 23
- 2023Reinforcement Learning from Automatic Feedback for High-Quality Unit Test Generationcited by 21
- 2024AI-Assisted Assessment of Coding Practices in Modern Code Reviewcited by 16
- 2025Challenges and Paths Towards AI for Software Engineeringcited by 11
- 2026AI Observability for Developer Productivity Tools: Bridging Cost Awareness and Code Qualitycited by 1
Built on by
Citing papers per year: 2026: 1.
1 paper.
- 2026From Agent Output to Authorized Transitioncited by 0
- 2026From Agent Output to Authorized Transition23 Sep 2026
Similar, not cited
Close in wording, no citation either way
- 2026SDAD: Spec-Driven Agentic Development for the AI-Native SDLC
- 2026How Do AI Coding Agents Contribute to Software Development? an Empirical Study of Agentic Pull Requests
- 2026Agentic Agile-V: From Vibe Coding to Verified Engineering in Software and Hardware Development
- 2026Reasoning effort, not tool access, buys first-try reliability in agentic code generation: an observational study
- 2026AI Writes Code, Humans Pay the Debt. An Empirical Study on the Sustainability and Evolution of Agent-Generated Code
- 2026A Lean and Spec-Driven AI-Assisted Software Development Lifecycle for Applied AI Education: The AI-SDLC Approach
- 2026Cheap Code, Costly Judgment: A Case Study on Governable Agentic Software Engineering
- 2026Rethinking Software Engineering for Agentic AI Systems