mlsanityData to 14 Oct 2026

Understanding Automated Program Repair Agents Through the Lens of Traceability: An Empirical Study

arXiv 2506.08311 ↗First posted 10 Jun 2025cs.SE cs.AIcited by 16

On the map: LLM agents and tool use → Software engineering coding agents

Abstract (arXiv)

Automated Program Repair (APR) agents leverage large language models (LLMs) to autonomously diagnose and patch software bugs using planning, reasoning, and tools. Although these agents show strong performance on leaderboards such as SWE-bench, little is understood about how they take actions, where they fail, and how their behavior compares to human developers. In this paper, we present the first systematic analysis of these limitations using 5 state-of-the-art APR agents. We trace the full decision-making pipelines of the 5 APR agents across 500 real-world repair tasks, from issue description to patch validation. Our study reveals that, while agents excel at simple fixes, they struggle with logic-intensive bugs, often generating verbose, overfitted patches that pass existing test suites without solving the root cause. Test generation and regression test selection remain major bottlenecks, as agents fail to reproduce issues or run relevant regression tests. Moreover, many agents operate with primitive tooling (e.g. bash scripts) and do not have access to debuggers or program analysis tools. These findings highlight key limitations of current APR systems and motivate several directions for next-generation APR design, including but not limited to: (1) a shift-left approach emphasizing early, high-quality test generation and validation to reduce spurious fixes and improve semantic correctness; (2) richer, more integrated tool ecosystems; (3) diversified agent architectures that combine complementary strengths; and (4) benchmarks that prioritize semantic repair quality and test-generation fidelity over surface-level success metrics.

Key facts. Cited by 16 papers 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 25 of its 63 references that are in the map. First posted on arXiv 10 Jun 2025.

Builds on

25 of 63 references.

Closest ancestors · 8

Same direction, newest first

  1. 2025Guided Search Strategies in Non-Serializable Environments with Applications to Software Engineering Agents19 May
  2. 2025Evaluating Agent-based Program Repair at Google13 Jan
  3. 2024Evaluating Software Development Agents: Patch Patterns, Code Quality, and Issue Complexity in Real-World GitHub Scenarios16 Oct
  4. 2024SpecRover: Code Intent Extraction via LLMs5 Aug
  5. 2024OpenHands: An Open Platform for AI Software Developers as Generalist Agents23 Jul
  6. 2024Agentless: Demystifying LLM-based Software Engineering Agents1 Jul
  7. 2024SWT-Bench: Testing and Validating Real-World Bug-Fixes with Code Agents18 Jun
  8. 2024MASAI: Modular Architecture for Software-engineering AI Agents17 Jun

Other references · 17

  1. 2023SWE-bench: Can Language Models Resolve Real-World GitHub Issues?cited by 3,373
  2. 2024AutoCodeRover: Autonomous Program Improvementcited by 278
  3. 2025SWE-RL: Advancing LLM Reasoning via Reinforcement Learning on Open Software Evolutioncited by 263
  4. 2022Grounded Copilot: How Programmers Interact with Code-Generating Modelscited by 218
  5. 2025Multi-SWE-bench: A Multilingual Benchmark for Issue Resolvingcited by 171
  6. 2022Large Language Models are Few-shot Testers: Exploring LLM-based General Bug Reproductioncited by 111
  7. 2024IRIS: LLM-Assisted Static Analysis for Detecting Security Vulnerabilitiescited by 103
  8. 2025S*: Test Time Scaling for Code Generationcited by 98
  9. 2023A Large-Scale Survey on the Usability of AI Programming Assistants: Successes and Challengescited by 75
  10. 2019TBar: Revisiting Template-based Automated Program Repaircited by 65
  11. 2025Are "Solved Issues" in SWE-bench Really Solved Correctly? An Empirical Studycited by 49
  12. 2024TDD-Bench Verified: Can LLMs Generate Tests for Issues Before They Get Resolved?cited by 34
5 more
  1. 2024Using AI Assistants in Software Development: A Qualitative Study on Security Practices and Concernscited by 28
  2. 2017Identifying Patch Correctness in Test-Based Program Repaircited by 17
  3. 2024Examining the Use and Impact of an AI Code Assistant on Developer Productivity and Experience in the Enterprisecited by 17
  4. 2019Characterizing Developer Use of Automatically Generated Patchescited by 1
  5. 2024Towards Understanding the Bugs in Solidity Compilercited by 1

Built on by

Cited by year (2026 to 14 Oct)

Citing papers per year: 2025: 4; 2026: 12.

16 papers.

Sort:

By area:

  1. 2025Understanding Code Agent Behaviour: An Empirical Study of Success and Failure Trajectoriescited by 33
  2. 2026Inside the Scaffold: A Source-Code Taxonomy of Coding Agent Architecturescited by 18
  3. 2026Rethinking the Value of Agent-Generated Tests for LLM-Based Software Engineering Agentscited by 14
  4. 2026Beyond Resolution Rates: Behavioral Drivers of Coding Agent Success and Failurecited by 11
  5. 2026AgentStepper: Interactive Debugging of Software Development Agentscited by 9
  6. 2025Dissecting the SWE-Bench Leaderboards: Profiling Submitters and Architectures of LLM- and Agent-Based Repair Systemscited by 8
  7. 2025A Comprehensive Empirical Evaluation of Agent Frameworks on Code-centric Software Engineering Taskscited by 7
  8. 2026Fail-Fast, Restart-Smart: Early Failure Prediction and Restart for SWE Agentic Taskscited by 5
  9. 2025Code Reasoning for Software Engineering Tasks: A Survey and A Call to Actioncited by 4
  10. 2026RepoMirage: Probing Repository Context Reasoning in Code Agents with Perturbationscited by 3
  11. 2026The Devil Is in the Interface: Evaluating How Tool Architecture Shapes Coding Agent Behaviorcited by 3
  12. 2026"Refactoring Runaway": Understanding and Mitigating Tangled Refactorings in Coding Agents for Issue Resolutioncited by 1
4 more
  1. 2026Terminal Agents: A Survey of AI Agents in Command-Line Environmentscited by 1
  2. 2026Validation Evidence in LLM Repair Agents: How Much of What Passes Actually Tests the Bug?cited by 0
  3. 2026Trajectory-Aware Benchmark Subset Selection for Cost-Efficient Software Engineering Agent Regression Testingcited by 0
  4. 2026Analyzing and Mitigating Cost-Inefficient Behaviors in Coding Agentscited by 0

Similar, not cited

Close in wording, no citation either way

  1. 2026EviACT: An Evidence-to-Action Framework for Agentic Program Repair
  2. 2024RepairAgent: An Autonomous, LLM-Based Agent for Program Repair
  3. 2026Multi-Perspective Agentic Program Repair via Code Property Graphs and Temporal Execution Graphs
  4. 2026Kozuchi Agent: A Language-Agnostic Open-Weight Agent for Software Repair
  5. 2024An Empirical Study on LLM-based Agents for Automated Bug Fixing
  6. 2025REFINE: Enhancing Program Repair Agents through Context-Aware Patch Refinement
  7. 2026TraceView: Interactive Visualization of Agentic Program Repair Trajectories
  8. 2026To Run or Not to Run: Analyzing the Cost-Effectiveness of Code Execution in LLM-Based Program Repair