Make Every Expansion Count: Learning to Search Efficiently in LLM Code Repair
Not on the map. Why?
Abstract (arXiv)
Large language model (LLM) code-repair systems fix faulty programs by repeatedly generating and testing revisions. Each revision is costly, making the choice of which repair to pursue important for efficiency. Existing search policies rely on test pass rates and search statistics, ignoring the details of test failures and proposed edits. We introduce CodeTriage, a learned policy that prioritizes edits before their revised programs are generated and tested. Its 0.6B-parameter model reads the test output, failure diagnosis, and proposed edit, then predicts a distribution over the number of repair steps needed to reach a fix through that edit. These predictions prioritize all pending edits across programs before generating and testing the revised code. On held-out repair tasks, CodeTriage finds fixes with 21% fewer program revisions and 12% fewer output tokens than the strongest baseline on each metric. Without retraining, it achieves the highest average success across search budgets for each of 11 unseen repair LLMs. Ablations show that both the failure context and edit text, as well as comparisons across programs, improve search. We also release a corpus of 12.2 million program versions from four LLMs, organized into repair trees with proposed edits and test results.
Key facts. No citing papers in the map yet (data through 14 Oct 2026). Builds on 30 of its 40 references that are in the map. First posted on arXiv 11 Oct 2026.
Builds on
30 of 40 references.
References · 30
- 2021LoRA: Low-Rank Adaptation of Large Language Modelscited by 14,380
- 2021Training Verifiers to Solve Math Word Problemscited by 10,109
- 2025Qwen3 Technical Reportcited by 8,820
- 2023Reflexion: Language Agents with Verbal Reinforcement Learningcited by 4,276
- 2023Let's Verify Step by Stepcited by 3,789
- 2023Tree of Thoughts: Deliberate Problem Solving with Large Language Modelscited by 3,211
- 2024Scaling LLM Test-Time Compute Optimally can be More Effective than Scaling Model Parameterscited by 1,986
- 2022Competition-Level Code Generation with AlphaCodecited by 1,462
- 2025gpt-oss-120b & gpt-oss-20b Model Cardcited by 1,386
- 2024Large Language Monkeys: Scaling Inference Compute with Repeated Samplingcited by 991
- 2023Teaching Large Language Models to Self-Debugcited by 988
- 2021Measuring Coding Challenge Competence With APPScited by 902
18 more
- 2022Solving math word problems with process- and outcome-based feedbackcited by 901
- 2023Reasoning with Language Model is Planning with World Modelcited by 861
- 2026GLM-5: from Vibe Coding to Agentic Engineeringcited by 587
- 2023Language Agent Tree Search Unifies Reasoning Acting and Planning in Language Modelscited by 574
- 2025SmolLM2: When Smol Goes Big -- Data-Centric Training of a Small Language Modelcited by 335
- 2026Gemma 4 Technical Reportcited by 259
- 2023Is Self-Repair a Silver Bullet for Code Generation?cited by 197
- 2023TACO: Topics in Algorithmic COde generation datasetcited by 160
- 2024SWE-Search: Enhancing Software Agents with Monte Carlo Tree Search and Iterative Refinementcited by 132
- 2025KodCode: A Diverse, Challenging, and Verifiable Synthetic Dataset for Codingcited by 119
- 2025Nemotron 3 Nano: Open, Efficient Mixture-of-Experts Hybrid Mamba-Transformer Model for Agentic Reasoningcited by 104
- 2026Qwen3-Coder-Next Technical Reportcited by 71
- 2026Nemotron-Cascade 2: Post-Training LLMs with Cascade RL and Multi-Domain On-Policy Distillationcited by 60
- 2024Code Repair with LLMs gives an Exploration-Exploitation Tradeoffcited by 51
- 2025Wider or Deeper? Scaling LLM Inference-Time Compute with Adaptive Branching Tree Searchcited by 51
- 2026Nemotron 3 Super: Open, Efficient Mixture-of-Experts Hybrid Mamba-Transformer Model for Agentic Reasoningcited by 38
- 2024CodeTree: Agent-guided Tree Search for Code Generation with Large Language Modelscited by 34
- 2026Aligning Tree-Search Policies with Fixed Token Budgets in Test-Time Scaling of LLMscited by 4
Built on by
Not cited yet.