ActionEngine
ActionEngine: From Reactive to Programmatic GUI Agents via State Machine Memory
Hongbin Zhong, Fazle Faisal, Luis França, Tanakorn Leesatapornwongsa, Adriana Szekeres, Kexin Rong, et al. · 2026-02-24
- Management
- T2 Dynamic Memory
- Memory changes during deployment through a stable management policy.
- Representation
- Cross-represented explicit
How experience becomes memory
Each path is one memory component, traced from what is stored to how it is found again.
updatable GUI state-machine memory
- Represented asSpatial, temporal & cross-modal structured memoryCross-represented explicit
- Stored inGraph / relational store
- Retrieved byStructure traversal, Planner / tool-assisted retrieval
- Source evidenceSource linked & recoverable
Crawler-validated GUI states and action templates form a state machine used to synthesize executable programs.Full paper: System Overview · PDF p. 2 · Figure 1
How memory changes (T2 operations)
Update · Rule-based update
Execution failures trigger fixed vision-based re-grounding and persistent memory updates. For ActionEngine, this specifically supports fixed-rule insertion or replacement of updatable GUI state-machine memory.
Revision · Rule-based state correction
Failed actions are repaired and their state-machine entries corrected. For ActionEngine, this specifically supports fixed-rule correction of stored state of updatable GUI state-machine memory.
Related systems
- MobiMemT3 · GUI & computer use
- Adaptive Workflow AgentsT2 · GUI & computer use
- Agent ST2 · GUI & computer use
- ATMemT2 · GUI & computer use
- AutoMMemoT2 · GUI & computer use
- Darwinian MemoryT2 · GUI & computer use