Search papers, labs, and topics across Lattice.
Existing personal GUI agents append task-relevant history to the policy's context, but this benefit is largely confined to the initial decision, offering minimal sustained guidance. This paper introduces ExpActivator, a training-free framework that recasts personalization as experience activation, selectively retrieving and utilizing historical experience only when it is applicable to the current decision context. ExpActivator significantly improves within-trajectory step success, reduces history token usage, and enhances proactive suggestion accuracy compared to prior methods.
Personal GUI agents waste most of their retrieved history; this framework activates experience only when it's actually applicable, boosting performance and efficiency.
Personal Graphical User Interface (GUI) agents rely on interaction history to infer what a user wants from ambiguous instructions and to anticipate recurring routines. Existing approaches retrieve task-relevant history and append it to the policy's context, implicitly assuming that experience relevant to a task remains useful for each decision within it. We find that this help is largely spent at the first decision: retrieved history strongly improves the opening step of an episode, yet provides little sustained benefit over the remaining 90\% of steps, and offers weak guidance on whether a proactive suggestion is warranted. A relevant record may tell the agent where to begin, but not which past action applies to the current screen or whether a routine is due now. The underlying issue is that relevance does not imply applicability}: relevance is determined at the task level, whereas applicability depends on the situation at decision time. We therefore recast personalization as experience activation and introduce ExpActivator, a training-free framework that activates only the experience applicable to the current situation. During execution, ExpActivator matches each new screen to historical states in the frozen GUI backbone's latent space and supplies the corresponding action as a reference. Before execution, it activates a recurring intent only when the current time and scenario provide sufficient support, and otherwise abstains. Across four GUI backbones, ExpActivator improves within-trajectory step success by 28\% on average, achieves the best personalized execution on every backbone while using about one-fifth as many history tokens, and reaches approximately 2.3$\times$ the Matthews correlation coefficient of the strongest proactive baseline. Experience pays where it is activated, not where it is appended.