- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper conducts research on three key issues faced by long-range Mobile GUI Agent in cross-application and multi-step tasks: the continuous growth of historical context makes it difficult to effectively retrieve early key evidence; the latent errors generated during execution may only be exposed in subsequent steps, making it challenging to accurately pinpoint the root cause; and erroneous or unverified execution trajectories may further contaminate the experience database, affecting the Agent's continuous self-improvement. To address these issues, the authors propose a unified CausGUI framework, which explicitly records sub-goals, execution steps, observed evidence, and their dependencies using Causal Ledger, and design three collaborating modules. The authors have also demonstrated the effectiveness of this framework through experiments.
Critical strengths
The research motivation is clear, and the framework design has good systematicity. The paper conducts research on the problems in long-term GUI Agent, such as the difficulty in effectively utilizing historical evidence, the inability to trace implicit execution errors, and the impact of erroneous experiences on subsequent self-evolution. The author designs a unified Causal Ledger, enabling Dependency Resolver, Attribution Auditor, and Self-Evolution Curator to share structured historical evidence and their dependencies, integrating context management, error attribution, and self-evolution experience into a complete execution and learning loop.
The experiments are quite comprehensive, and the core mechanism has been verified specifically. The author conducted extensive comparisons on multiple benchmarks and different scales of Backbones, achieving stable performance improvements. In addition to incremental ablation to verify the effectiveness of each module, special experiments such as root cause localization, dependency-aware context management, experience admission and elimination, etc., were also conducted to further analyze the contribution of the core mechanism. Moreover, multi-round self-evolution and unseen task migration experiments also demonstrated the potential of the framework in continuous experience accumulation and combination generalization within the same application ecosystem. The overall experimental argumentation is quite solid.
Critical weaknesses
The paper integrates context-aware dependency perception, error attribution, and experiential self-evolution through a unified Causal Ledger, demonstrating certain system innovation value. However, its basic design is still mainly based on existing task planning, structured memory, execution verification, and experience management mechanisms, and causal dependencies are mainly constructed through explicitly declared evidence support relationships in the model. Therefore, compared to a complete system design, the independent innovation of a single algorithm mechanism is relatively limited.
Although the author verified the effectiveness of experience in unseen tasks through MobileWorld-XL, this benchmark shares the application ecosystem with the original MobileWorld and mainly demonstrates the combined generalization ability. Further verification of the effect of experience transfer in different application environments will help to more comprehensively evaluate the generalization ability of the proposed self-evolution mechanism.
Questions for authors
Table 2 demonstrates the improvement in the final task success rate achieved by the Attribution Auditor. Appendix B.6 also confirms the advantage of dependency graph backtracking in root cause identification. However, the Auditor simultaneously includes step-level verification, sub-goal review, and dependency graph backtracking. It is not clear to what extent the final success rate improvement is attributed to the dependency graph backtracking itself. Could the authors further explain or conduct more detailed ablation studies to distinguish the individual contributions of the verification execution and causal backtracking?