- Rating
- 4(+1)
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper studies how to improve long-horizon LLM agents when unsupported assumptions or outdated plans persist in their interaction histories. It proposes Agent-Editing World Model (AEWM), which judges the expected contribution of a proposed reasoning–action pair and replaces proposals classified as noisy before execution. The EditAct framework combines these interventions with real environment feedback while preserving the preceding history. A unified model learns judgment and revision across Search, Terminal, and Software Engineering through mid-training and supervised fine-tuning. Experiments on six benchmarks and three agent backbones show average-score gains of 3.2–6.7 points over the strongest reported baseline. Fine-tuning agents on verified EditAct trajectories also improves performance without online AEWM guidance.
Critical strengths
-
A valuable motivation and a concrete intervention mechanism. Real tool feedback does not necessarily correct an agent's mistaken interpretation or outdated plan. The paper addresses this problem by judging proposed decisions and jointly revising their reasoning and actions before execution. I find this a useful direction for world modeling in tool-using agents. The distinction between productive exploration and noisy decisions is also well motivated.
-
Broad evaluation with informative ablations. The results cover three domains, six benchmarks, and three agent backbones. The ablations examine random intervention, resampling, hint-based guidance, separate reasoning and action revision, and model substitution. These comparisons support the value of learned intervention selection and joint revision. The AEWM-RFT results further show that the resulting trajectories provide useful supervision for agents that subsequently run without AEWM guidance.
Critical weaknesses
-
Failure modes of online intervention remain underexplored. The aggregate results support a positive overall effect, and the paper provides successful intervention cases and search-behavior statistics. However, Section 5.2 explicitly focuses on selected successful interventions, leaving limited analysis of ineffective revisions or useful exploration mistakenly classified as noisy. This makes it difficult to assess when intervention may be unnecessary or counterproductive. (Lines 424–431; Figure 4; Appendix D, lines 1244–1249.)
-
The stability of smaller gains and the actual inference costs are unclear. The paper reports means over three independent runs without measures of variability. Some differences are modest: on BrowseComp, Full AEWM scores 48.1 versus 47.4 for DeepSeek-V4-Pro WM. The appendix specifies evaluation budgets and generation limits, but does not report average total token usage, model calls, or wall-clock time. These omissions limit the interpretation of smaller improvements and the performance–cost trade-off. (Lines 305–307; Table 3, lines 334–340; lines 1130–1133; Table 13, lines 1134–1143.)
Questions for authors
-
Failure and ineffective-intervention analysis: Could you provide examples or a small audit of failed or ineffective online interventions, particularly cases where useful exploration is incorrectly classified as NOISY? Please describe the observed consequences of these revisions for subsequent task progress and how the cases were selected. This would help clarify the method's reliability and failure boundaries. A small analysis of existing trajectories would help make these limitations more concrete. (Lines 424–431; Appendix D, lines 1244–1249.)
-
Stability and inference cost: How consistent are the reported gains across the three evaluation runs, and what inference cost is required to obtain them? Please report standard deviations or individual-run scores for the main comparisons, together with average per-task token usage, model-call counts, and wall-clock time for EditAct, ReAct, and Best@3 under the reported agent and task settings. Costs should include judgment, revision, and candidate-selection calls where applicable. This would help assess both smaller gains, such as the 0.7-point BrowseComp improvement over DeepSeek-V4-Pro WM, and the performance–cost trade-off. (Lines 305–307; Table 3, lines 334–340; lines 1130–1133; Appendix C.2–C.3, lines 1148–1224.)
5 comments
Thank you to the authors for your thoughtful responses and the additional results provided. Your previous answers have addressed some of the questions I initially raised. I would like to discuss a few further points:
-
What is the proportion of these two types of "classic" errors relative to the overall distribution of error types? Could you provide a statistical distribution of common errors?
-
Could you provide statistics on the transitions between ReAct and EditAct? Specifically, I am interested in the breakdown of task outcomes: success→failure, failure→success, success→success, and failure→failure. In my view, only a sufficiently granular evaluation and analysis can truly clarify the effectiveness of EditAct.
We sincerely thank the reviewer for the helpful follow-up questions. We further analyzed the common errors made by Action Judge and examined how EditAct changes task outcomes compared with ReAct, including both successful corrections and negative interventions.
1. Distribution of False-NOISY Errors
Our previous response focused on two specific failure cases. We have now extended this analysis to examine a broader range of errors and identify common failure patterns across three domains. Specifically, we analyze cases where Action Judge incorrectly classifies useful actions as NOISY. The table below shows the distribution of error types in each domain.
| Error Type | Search | Terminal | SWE |
|---|---|---|---|
| Necessary inspection mistaken for repetition | 30% | 45% | 15% |
| Untested behavior assumed correct | 0% | 10% | 35% |
| Useful exploration dismissed as low-value | 65% | 15% | 10% |
| Feasible tool operations incorrectly expected to fail | 5% | 20% | 10% |
| Necessary implementation or repair dismissed as unnecessary | 0% | 10% | 30% |
Search: Useful exploration is most frequently undervalued (65%). Action Judge sometimes rejects promising search directions because they appear indirect or unlikely to yield immediate answers. Necessary source checks are also mistaken for repetitive operations (30%), overlooking their value in verifying information.
Terminal: Necessary inspection is most frequently mistaken for repetition (45%). The previously discussed fix-git case illustrates this error: Action Judge rejected reading a conflicted file because an earlier version had already been inspected, overlooking the file's changed state. Another common error is incorrectly predicting that feasible tool operations will fail (20%).
SWE: Assuming untested behavior is correct (35%) and dismissing necessary implementation (30%) are the most common errors. The previously discussed doc2mark case illustrates the former: Action Judge assumed the public wrappers worked because the underlying loader had been tested, incorrectly rejecting a necessary verification step. It also sometimes dismisses necessary implementation or repair as unnecessary.
These findings also highlight directions for further improving AEWM in future work, particularly in recognizing the value of exploration, identifying when additional verification is necessary, and avoiding unsupported assumptions about untested functionality.
2. Paired ReAct → EditAct Outcomes
To better understand the effectiveness of EditAct, we analyze how task outcomes change from ReAct to EditAct, considering both improvements and regressions. For BrowseComp and Terminal-Bench 2.0, we examine transitions between task success and failure. For Doc2Repo, we analyze changes in test pass rates.
The results are summarized below.
| Benchmark | Success→Failure | Failure→Success | Success→Success | Failure→Failure |
|---|---|---|---|---|
| BrowseComp | 7.27% | 14.51% | 33.60% | 44.63% |
| Terminal-Bench 2.0 | 4.12% | 15.36% | 32.96% | 47.57% |
EditAct converts substantially more failed tasks into successful ones than the reverse. On BrowseComp, 14.51% of comparisons change from failure to success, approximately twice the 7.27% that change from success to failure. On Terminal-Bench 2.0, this difference is even larger: 15.36% improve from failure to success, compared with only 4.12% that regress.
The success-to-failure transitions also reflect the risks of incorrect interventions discussed in Question 1: useful actions may be mistakenly classified as NOISY and replaced with less effective decisions. Nevertheless, EditAct corrects substantially more failures than the regressions it introduces, demonstrating that AEWM-guided decision correction provides a clear overall benefit to task-solving performance.
For Doc2Repo, we analyze whether EditAct increases or decreases the test pass rate:
| Test Pass-Rate Change (ReAct → EditAct) | Percentage |
|---|---|
| Increases | 48% |
| Decreases | 29% |
| Unchanged | 23% |
EditAct also improves Doc2Repo performance in both the frequency and magnitude of positive changes. Test pass rates increase in 48% of comparisons, compared with 29% showing decreases. Moreover, the average improvement is larger than the average decline (20.88 vs. 13.35 percentage points), contributing to the overall performance increase from 42.8% to 48.9%.
Overall, the results consistently show that EditAct produces more positive changes than negative ones across all three benchmarks. In particular, its ability to turn failed tasks into successful ones demonstrates the effectiveness of AEWM-guided decision correction in improving agent task-solving performance.
We sincerely thank the reviewer again for the valuable suggestions. We will incorporate these additional analyses and findings into the revised version of our paper.
We sincerely thank the reviewer for the thoughtful feedback and constructive suggestions. We appreciate the recognition of our motivation and experimental results. Below, we provide additional analysis of ineffective interventions and report further results on performance stability and inference costs.
Q1. Failed and ineffective interventions
Table 11 reports 72.5% overall prediction accuracy on our Action Judge benchmark, corresponding to 27.5% classification errors. We identify two representative failure patterns in which useful actions are incorrectly classified as NOISY:
1. Incorrectly skipping a necessary file inspection. In the Terminal task
fix-git, the agent needed to recover a lost commit and integrate its changes into the main branch. Applying the commit produced a merge conflict. The agent proposed reading the conflicted file, a useful step for understanding the current conflict before editing it. Action Judge classified this inspection as NOISY because earlier versions of the file had already been viewed and the intended incoming changes were known. State Revision replaced reading the file with listing the names of conflicted files. This revealed no conflict content, so the agent read the file in the next step anyway. The task ultimately succeeded, but the intervention introduced an unnecessary detour. The underlying error was treating earlier knowledge of the file as sufficient after its state had changed.2. Incorrectly assuming an untested function works correctly. In Doc2Repo's
doc2marktask, the agent was reconstructing a document-conversion library. A first test of its public convenience functions failed because an API key was missing. The agent proposed rerunning those functions with an explicit API-key argument, which would check the public wrappers' argument handling and execution. Action Judge classified this as NOISY, reasoning that the wrappers were already correct because their underlying loader had been tested. State Revision instead supplied the key through an environment variable and generated a malformed shell command. The command failed before performing the test, requiring another verification step. The revision therefore delayed useful validation and left the proposed explicit-argument path unchecked at that point. Here, confidence in one component prematurely displaced evidence about another interface.Q2. Stability and inference cost
We additionally report the standard deviations across three independent runs, together with token usage, for Qwen3.5-35B-A3B. Tokens represent total model tokens per task, in millions.
The reported standard deviations indicate reasonably consistent performance across runs, despite some task-dependent variation. The additional token cost relative to ReAct mainly arises from Action Judge and State Revision processing the interaction history again, increasing input-token usage. Compared with the Best@3 baselines, EditAct achieves better performance across all three tasks, using fewer tokens than trajectory-level Best@3 and remaining within the same order of magnitude as step-level Best@3, albeit with higher token usage. These results highlight the effectiveness of targeted decision correction while making the associated performance–cost trade-off explicit.