๊ฐ€์ž… ํ›„ ์ดˆ๋Œ€ ๋งํฌ๋ฅผ ๊ณต์œ ํ•˜๋ฉด ๋™์˜์ƒ ์žฌ์ƒ ๋ฐ ์ดˆ๋Œ€ ๋ณด์ƒ์„ ๋ฐ›์„ ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

cv usk
@cv_usk
AI / Software Research Notes AI Agent, LLMOps, MLOps, Software Architecture ๆŠ•็จฟใฏๅ€‹ไบบใฎๆ„่ฆ‹ใงใ™ใ€‚
๊ฐ€์ž… May 2026
258 ํŒ”๋กœ์ž‰ ์ค‘    220 ํŒฌ
๐Ÿค– Mobile GUI agents are fine on short tasks but fall apart on long, multi-step ones. The reason is simple: just piling up action and screenshot history blows up the context and dilutes the cross-app information that actually matters. This work's idea is to promote context management from "passively accumulating history" to "an action the agent deliberately chooses." Just as it picks a UI operation, the agent can also choose to fold its history and UI state. It keeps three structured fields โ€” folded action history, folded UI state, and a recent step record โ€” balancing the overall arc with the immediate details. That's the Context-as-Action framework, MemGUI-Agent. ๐ŸŽฏ It's trained on MemGUI-3K (2,956 annotated trajectories), producing the 8B MemGUI-8B-SFT via supervised fine-tuning. The result reaches best open-data 8B performance on MemGUI-Bench and generalizes to the out-of-distribution MobileWorld benchmark. Letting the agent itself decide what to keep and what to fold feels broadly useful for any production agent fighting context bloat. MemGUI-Agent: An End-to-End Long-Horizon Mobile GUI Agent with Proactive Context Management #GUIAgents# #LLM#
๋” ๋ณด๊ธฐ