- Rating
- 2
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
LocalLSTC addresses long-horizon GUI-agent control by maintaining an explicit persistent state for the active subgoal, accumulated evidence, and runtime feedback. Long-to-Short Planning uses this state to form a bounded short-term execution commitment; Short-to-Long Control abstracts execution outcomes and updates the state for progress assessment, recovery, and termination. The authors evaluate on OSWorld and WindowsAgentArena, report gains with local backbones, annotate cross-step control failures, and ablate L2S, S2L, and runtime components. The paper reports 73.7% SR-100 on OSWorld and 68.5% on WindowsAgentArena with Qwen3.8-27B.
Critical strengths
-
The paper addresses practical challenges in long-horizon desktop automation. It targets stage tracking, progress assessment, action repetition, recovery, and premature termination, particularly for locally deployed models.
-
The evaluation combines benchmark results with mechanistic analysis. It includes OSWorld and WindowsAgentArena results, fixed-backbone L2S/S2L ablations, runtime diagnostics, and partial human validation of trajectory annotations.
Critical weaknesses
- The paper’s novelty boundary remains unclear. Its candidate contribution is the closed-loop combination of persistent task state, bounded multi-action commitments, and evidence-driven routing/recovery. Related mechanisms appear in TSR, ATMem, HiSA, VLAA-GUI, CES, CoAct-1, and ActionEngine. Direct comparisons and ablations are needed to establish the combination’s incremental value.
- Evidence for comparative advantage and failure attribution is limited.
Questions for authors
- How does LocalLSTC’s state/commitment/routing loop differ from TSR, ATMem, and CoAct-1? What incremental gain does the existing CoAct-1 comparison show for state updates and routing?
- Which ablations support each claimed contribution? Since removing state-conditioned routing also disables recovery/stall handling and final verification, how can their effects be separated? Which components are inherited from HiSA?
- Does the 22-percentage-point reduction in ANY incidence (63.7% baseline average vs. 41.7% for LocalLSTC) persist with human-adjudicated or uncertainty-aware labels? Please quantify uncertainty in this difference.
We thank the reviewer for the detailed comments on novelty, comparative evidence, and failure attribution. We combine the closely related weaknesses and questions below.
Weakness 1 and Questions 1–2
LocalLSTC builds on existing mechanisms for Step Abstraction, Context Refinement, and hybrid GUI/Bash/API interaction. As described in Section 3.2.3, it extends HiSA's Step Abstraction from GUI execution to a unified, subgoal-aligned evidence interface covering GUI, Bash, and software APIs, and replaces HiSA's fixed-period Context Refinement with execution-state-triggered refinement. Its main contribution is the closed-loop organization of persistent task state, bounded short-term action commitments, and execution-evidence-driven control.
Specifically, L2S uses the persistent subgoal, accumulated evidence, and runtime feedback to generate and select a bounded action commitment. After execution, S2L abstracts the outcomes, updates the persistent state, and uses state-conditioned rules to determine subsequent progress assessment, refinement, recovery, and termination. The updated state then informs the next L2S planning step. This coupling allows planning and execution feedback to interact continuously throughout a task.
Existing approaches address related aspects of this process. TSR maintains an instruction summary, subgoal progress, and a transition-aware verifier, updating task state through visual observations before and after actions. ATMem maintains structured memory of task-relevant information, including its workflow roles and execution status, and uses STR-GRPO to train the model to access this memory selectively. HiSA provides Step Abstraction and Context Refinement. CoAct-1 coordinates GUI and coding agents through subtask delegation, with execution results summarized and returned to an orchestrator. We will expand the discussion of these approaches, together with VLAA-GUI, CES, and ActionEngine, to make the relationship between existing techniques and our proposed organization more explicit.
Under the same Qwen3.5-9B planning backbone, LocalLSTC achieves 45.4% mean SR-100, compared with 34.2% for CoAct-1 and an average of 36.0% across the four baseline frameworks. This is an improvement of 11.2 percentage points over CoAct-1 and 9.4 points over the baseline average. Evidence for the proposed mechanisms comes from the grouped and component ablations below. Each reported drop is computed from the corresponding two-run mean.
No current ablation isolates the routing decision rule alone. State-conditioned routing determines when to invoke recovery, stall handling, Final Verification, and Context Refinement, and these operations are coupled to routing within the proposed control mechanism. Retaining them while removing the routing rule would require an alternative scheduler and would therefore evaluate a different control design. The routing ablation measures the integrated routing-dependent package, while the grouped L2S and S2L ablations provide the primary evidence for the complete mechanisms and the remaining component ablations examine their constituent operations. We will clarify these dependencies and the scope of each ablation in the revision.
Weakness 2 and Question 3
We conducted paired task-level bootstrap analyses to quantify uncertainty in the reported ANY incidence difference. For the human validation subset, two annotators independently labeled the trajectories. Since no adjudicated consensus labels were collected, we report the results for each annotator and their average separately.
On the whole set, the GPT annotations give an ANY-incidence difference of 24.86 points. On the human-validation subset, the corresponding differences are 6.25 points for Annotator 1 and -0.69 points for Annotator 2, with an average difference of 2.78 points. The table reports paired-bootstrap 95% confidence intervals for each estimate.