mlsanityData to 7 Oct 2026

What Makes Software Issue Resolution Tasks Difficult for Agents?

arXiv 2608.18280 ↗First posted 18 Aug 2026cs.SE cs.AI cs.CLcited by 0

Not on the map. Why?

Abstract (arXiv)

Background. Advances in agentic systems are simultaneously, and rapidly, saturating benchmarks. Despite this often discussed phenomena, benchmark scores remain difficult to interpret due to the lack of control and characterization of task difficulty. More specifically, we currently have little understanding of what makes one task harder than another, and to what extent task difficulty is predictable from static task properties. Aims. We propose a measurement framework to investigate and systematically quantify what structural properties of software tasks correspond to agent success rates for issue resolution tasks. Method. We conducted a large scale empirical study on CoderForge-Preview, the largest open dataset of coding agent trajectories to date, by extracting features across task patch, repository and prompt. We evaluated the predictive power of each feature against task outcomes using ensemble methods, SHAP attribution, and effect size analysis. Results We found that task difficulty is substantially predictable from static features (AU C = 0.863) and is largely driven by patch fragmentation and repository scale. Prompt linguistic features become visible among top contributors for tasks in the mid-band, revealing a layered structure of difficulty. Conclusion. The difficulty of an issue resolution task is encoded in its structure. This enables static, pre-hoc difficulty estimation and lays the groundwork for difficulty-controlled benchmark construction for evaluation of agents.

Key facts. No citing papers in the map yet (data through 7 Oct 2026). Builds on 16 of its 38 references that are in the map. First posted on arXiv 18 Aug 2026.

Builds on

16 of 38 references.

References · 16

  1. 2025Qwen3 Technical Reportcited by 8,195
  2. 2017A Unified Approach to Interpreting Model Predictionscited by 6,488
  3. 2023SWE-bench: Can Language Models Resolve Real-World GitHub Issues?cited by 3,193
  4. 2026Terminal-Bench: Benchmarking Agents on Hard, Realistic Tasks in Command Line Interfacescited by 515
  5. 2024tinyBenchmarks: evaluating LLMs with fewer examplescited by 295
  6. 2025SWE-smith: Scaling Data for Software Engineering Agentscited by 255
  7. 2025SWE-Bench Pro: Can AI Agents Solve Long-Horizon Software Engineering Tasks?cited by 254
  8. 2025R2E-Gym: Procedural Environments and Hybrid Verifiers for Scaling Open-Weights SWE Agentscited by 140
  9. 2025SWE-rebench: An Automated Pipeline for Task Collection and Decontaminated Evaluation of Software Engineering Agentscited by 127
  10. 2025UTBoost: Rigorous Evaluation of Coding Agents on SWE-Benchcited by 44
  11. 2025Fluid Language Model Benchmarkingcited by 30
  12. 2025Reliable and Efficient Amortized Model-based Evaluationcited by 29
4 more
  1. 2025GSO: Challenging Software Optimization Tasks for Evaluating SWE-Agentscited by 24
  2. 2026BenchGuard: Who Guards the Benchmarks? Automated Auditing of LLM Agent Benchmarkscited by 13
  3. 2025When Prompts Go Wrong: Evaluating Code Model Robustness to Ambiguous, Contradictory, and Incomplete Task Descriptionscited by 8
  4. 2026Agent psychometrics: Task-level performance prediction in agentic coding benchmarkscited by 8

Built on by

Not cited yet.

Similar, not cited

Close in wording, no citation either way

  1. 2026What Does an Agentic Software Engineering Benchmark Measure? Profiling Task Demands and Agent Behaviour Beyond What Category Labels Reveal
  2. 2026Beyond Resolution Rates: Behavioral Drivers of Coding Agent Success and Failure
  3. 2025Understanding Code Agent Behaviour: An Empirical Study of Success and Failure Trajectories
  4. 2026ContextBench: A Benchmark for Context Retrieval in Coding Agents
  5. 2026The Devil Is in the Interface: Evaluating How Tool Architecture Shapes Coding Agent Behavior
  6. 2025An Empirical Study on Failures in Automated Issue Solving
  7. 2026Coding-Agent Benchmarks Should Match Their Users' Task Flows
  8. 2025Process-Centric Analysis of Agentic Software Systems