← All papers  /  Oct 8, 2026
Agents · Memory

DeltaReplay: Task-Relative Memory Reuse for Mobile GUI Agents

First page
DeltaReplay: Task-Relative Memory Reuse for Mobile GUI Agents
The curator’s take

Yudong Bai, Quanming Yao, Yaqing Wang and colleagues (Tsinghua University) present DeltaReplay, which stores mobile GUI trajectories as paths in a page-transition graph and decides at each step whether to replay a recorded action, replay it with new parameters, or hand control to the base agent.

Ask this paper

Key points
01

Reuse depends on the new task. A stored record's reusable part depends on how it relates to the new task, mainly page-level consistency and action-level generality. Each recorded action is split into a task-independent operation and task-specific parameters.

02

Partial matches. Records from the same template replayed verbatim solve 9.1% of tasks, ignoring them leaves the base agent at 63.6%, and DeltaReplay's step-level reuse with parameter replacement reaches 86.4%.

03

Irrelevant memory hurts. When memory holds only weakly related tasks, adding retrieved records to the prompt lowers success from 39.6% to 25.0%. DeltaReplay leaves such steps to the base agent.

04

Results. With the same backbone it improves success over the base agent by up to 10.3 points on AndroidWorld and 25.0 points on SPA-Bench, surpasses GUI-Owl-1.5, and cuts per-step latency from 21.7 s to 9.3 s on same-task reuse.

Abstract

Memory-augmented mobile GUI agents store successful execution trajectories and reuse them in later tasks, but a stored trajectory rarely matches a new task exactly. The new task may use different parameters, share only some of its steps with a stored trajectory, or have no relevant record in memory. Forcing the agent to use irrelevant memory can mislead it, whereas discarding memory that may still be useful deprives it of guidance from past experience. To address this dilemma, we propose DeltaReplay, a step-level memory reuse framework that decides how to use existing memory without modifying it. We observe that the reusable part of a stored record is determined not by the record itself but by its relation to the new task, mainly through two factors: page-level consistency and action-level generality. We therefore store execution trajectories as paths in a transition graph, whose nodes (pages) and edges (actions between pages) capture these two factors. At reuse time, the action on each edge is split into a task-independent operation and task-specific parameters. DeltaReplay then compares each recorded step with the new task and the current screen, and decides whether to follow it, execute it after replacing its parameters, or leave it to the base agent. On AndroidWorld and SPA-Bench, DeltaReplay improves the task success rate over a base agent with the same backbone by up to 10.3 and 25.0 percentage points, respectively. These results indicate that deciding at each step how to use retrieved memory lets agents benefit even from partially matching trajectories.

Every Monday
Get next week’s papers.
Subscribe on Substack