- Rating
- 2
- Confidence
- 3
- Informativeness
- 3(+1)
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper examines computer-use agents that perform an action again even though their own reasoning has already said the action failed, and it names this behavior inertia. Across four open agents, the activations before each action shift only slightly while the repetition lasts, and steering these activations does not lower it consistently. The proposed R3 clears the context once repetition is detected, looks for an action that alters the screen, and afterwards puts the earlier history back. Over 97 OpenComputer tasks, R3 lowers recurrence for every one of the four agents, while every task-score interval contains zero.
Critical strengths
- Recurrence is measured in a simple and repeatable way, since it relies on exact matches of screens and actions rather than on the judgment of an LLM (Section 2.1). The acknowledgment labels are validated against a second judge and against human annotation (Appendix B.3).
Critical weaknesses
-
It is unclear what is gained in practice by reducing inertia, since lower recurrence is not accompanied by a higher task score (Table 1). For OpenCUA with steering, recurrence and task score even rise at the same time.
-
Wan et al., Mitigating Conversational Inertia in Multi-Turn Agents (arXiv 2602.03664, ICML 2026), reduces the novelty of this paper; it is not cited here, and the two works overlap at three levels. On the phenomenon, Wan et al. describe inertia as an agent copying its earlier responses rather than adjusting to new feedback, which is similar to the repeated action examined here. On the analysis, Wan et al. find that from the same state a longer context produces stronger inertia than a shorter one, and the replay experiment carries out the same type of comparison between the full history and a fresh context (Table 2). On the method, their Clip Context empties the history once the context hits a threshold, which is also what the Reset step and the Permanent Reset baseline do. Wan et al. work with text-based agents and do not include the failure acknowledgment label, the activation analysis and steering, the recurrence trigger, or the Reroute and Restore steps. The paper should make this difference explicit and compare R3 against Clip Context.
-
The activation analysis yields no result that the input and the reasoning text do not already account for. The limited activation change during recurrence is consistent with attention copying from a repeated context, a mechanism the paper mentions but does not disentangle (Appendix A). The acknowledgment readout is read after reasoning that has already stated the failure, so separating the two classes is the expected outcome (Figure 4). In Figure 3, the activation change of GUI-Owl also remains around 30% for most of its recurrence run.
-
The evaluation is too narrow to tell whether the findings carry over to the latest agentic models that reason at length before acting. Each of the four agents is an open-source computer-use model whose visible reasoning is short (Appendix B.3), and the mitigation is tested on a single benchmark. Whether long-thinking agentic models display similar inertia remains unknown.
Questions for authors
-
Could the authors provide Table 1 under a single fixed setting shared by all agents and all methods? Both the R3 threshold and the steering strength vary from agent to agent, and the threshold is tuned on the evaluation tasks (Appendix D.2).
-
How well does the recurrence detector transfer outside the two benchmarks? It demands screens that match pixel for pixel, with only the clock region masked (Appendix B.2). Screens in real applications and in other domains frequently include dynamic content, which makes recurrence difficult to define this way and may leave many repeated actions undetected. Since this detector is what triggers R3, it restricts the generality of the method. Is there a definition of recurrence that does not rely on screens being exactly identical?