HAFixAgent: History-Aware Agentic Program Repair

arXiv:2511.01047 · cs.SE, cs.AI · Submitted 2025-11-02 · Read on arXiv

cs.SE, cs.AI

Submitted: 2025-11-02

Updated: 2026-10-08

Comments: Evaluation: on both realistic spectrum-based fault localization and perfect fault localization Benchmarks: Defects4J and BugsInPy Subject LLMs: DeepSeek-V3.2-Exp, Qwen3-Coder-Next, and Devstral-Small-2

Code: https://github.com/deepseek-ai/DeepSeek-V3.2-

License: http://creativecommons.org/licenses/by/4.0/

The gist: Automated program repair (APR) has recently shifted toward large language models and agent-based systems, while prior work shows that repository history can help repair single-line bugs.

Terminology

Abstract

Automated program repair (APR) has recently shifted toward large language models and agent-based systems, while prior work shows that repository history can help repair single-line bugs. We conduct a large-scale empirical study of whether, how much, and under what conditions repository history improves agentic APR beyond this setting. We present HAFixAgent, a history-aware program repair agent that injects blame-derived repository context into its repair loop. Across 854 Defects4J (Java) and 501 BugsInPy (Python) bugs, we first show that bug-relevant history is widely available. We then evaluate HAFixAgent across three base models under perfect fault localization. The best history heuristic improves over non-history from +4.4% on Defects4J and +1.1% on BugsInPy with the strongest model to as much as +64.3% with weaker models. HAFixAgent also outperforms RepairAgent by +56.6% and BIRCH-feedback by +47.1% on the strongest model, showing that it is a strong repair agent independent of history. The three history heuristics are complementary: each repairs a different subset of bugs, so their hybrid significantly repairs more bugs than non-history (McNemar's test, p < 0.001), and this advantage persists under realistic spectrum-based fault localization. Individual history heuristics are generally no more expensive than non-history in agent steps or tokens under either localization setting, while the hybrid costs roughly twice a single run in a cascade setting.

Sources

Related papers