- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper introduces a framework that aims to improve LLM context management during code repair tasks. The authors design a middle stage between the original data sources and the LLM, organizing information into structured evidence units that serve as the basis for agent-based code repair. The method is evaluated on well-known code repair benchmarks, including SWE-bench Lite and SWE-bench Verified, and the reported results show improvements in both repair performance and context efficiency over the evaluated baselines.
Critical strengths
-
Carefully designed dynamic context management method. The method models evidence selection, visibility, and reactivation as a state management problem across different stages of code repair tasks, which is a practical challenge in real-world software engineering.
-
Clear figures and well-written paper which is easy to understand and follow.
Critical weaknesses
-
The novelty of the method is limited. DySCoR mainly adds state-aware, and budget-constrained management to existing dynamic context retrieval methods. It remains unclear whether existing agents could achieve similar results through their own state management and dynamic retrieval mechanisms.
-
The selected baselines are not sufficiently competitive. Stronger code repair systems have already achieved much higher resolution rates on SWE-bench Lite and SWE-bench Verified. Evaluations on more competitive baselines will make the authors' method more convincing.
Questions for authors
Q1: As LLMs become larger and agent frameworks continue to advance, will the benefits of DySCoR become less significant? What advantages does it offer over the context management mechanisms of more advanced agents?
Q2: Can the proposed method provide similar improvements when integrated with stronger models and agents? DySCoR was not evaluated with larger and more capable LLMs.
Response to Reviewer 2gyt
Thank you for asking whether a stronger agent can already recover the same evidence on its own. We agree that the original baselines establish a gain within one repair workflow and leave that question open.
[Q1] What advantage can remain over native context management as the model and agent improve?
[A1] A capable agent may already reread the correct caller after a failed edit. In that case, an explicit reactivation rule could lead to the same repair. The possible remaining benefit is the cost of getting there, for example if the agent uses several reads to rediscover that caller. Conversely, a visibility rule that suppresses the caller can interfere with an effective native search. Both possibilities motivate measuring actual token use as well as success.
In the submitted workflow, file-level Hit@1 and Hit@5 are 54.8% and 72.4%. At function level they are 34.2% and 55.8%. The 21.6-point gap at function level measures cases in which a relevant function appears in positions two through five. Later feedback could move one of those functions into the next edit context. Whether a stronger agent would eventually read it anyway is the question addressed by the paired runs below.
[Q2] Can stronger models and more competitive agents obtain similar gains?
[A2] The original average gain of 4.5 percentage points compares DySCoR with ToolAgent+StaticPack under Qwen2.5-Coder-32B-Instruct. To test how the incremental gain changes with the backbone, the comparison below keeps mini-SWE-agent, the 100 Verified issues, and the budget ceilings fixed across all four conditions. Both backbones retain native tools and exploration.
claude-sonnet-4-5-20250929)For N issues, let w count issues solved only with DySCoR and l count issues solved only with native context. The signed change is 100(w−l)/N percentage points. The observed gain is +3.0 points with Qwen (6 wins, 3 losses) and +1.0 point with Sonnet (4 wins, 3 losses). On Sonnet, mean input falls from 810.0K tokens per issue with native context to 650.0K with DySCoR. With Claude Code and the same Sonnet snapshot, both configurations resolve 74.0%, while mean input falls from 880.0K to 735.0K. Across these two Sonnet comparisons, the more consistent benefit is lower input use. The change in repair success depends on the harness.