A unified execution model that maintains a work item's persistent identity and versioned authoritative state across calls is introduced that is associated with higher end-to-end pass rates across fresh sessions in this benchmark, at a measurable time cost.
Abstract
Agentic systems often organize execution and state around a single conversation, model invocation, or agent instance, even when real work spans many calls and stages. We introduce a unified execution model that maintains a work item's persistent identity and versioned authoritative state across calls. Each step receives input scoped to a specific state version and new material; a result advances state only after validation and recording. We implement selected paths of this model in AstronOS using Cases, Tasks, and Scenario Packs across central and local execution. We compare five complete strategies for carrying an established software-version update plan into a fresh model session: rereading original materials, replaying full history, deterministic text summary, deterministic JSON, and the AstronOS runtime-mediated handoff. Ten controlled tasks are run under all five strategies with three repetitions, yielding 150 included executions. On the single-stage reference family, strategies perform similarly. In the primary three-stage A-C batch, AstronOS passes the frozen scorer in 14 of 15 executions, compared with 0 of 15 for rereading and 2 of 15 for full-history replay; later non-interleaved summary and JSON batches each pass 0 of 15. AstronOS has lower attempt-accounted model-token cost per passing execution, while requiring more execution-window time per attempt. These results associate the complete AstronOS condition with higher end-to-end pass rates across fresh sessions in this benchmark, at a measurable time cost.
AgentRadio is presented, an asynchronous message-passing layer that equips coding-agent harnesses with three primitives: threads, messages, and waiting for mentions that shows the gain growing with task difficulty, consistent with mid-course correction as the underlying mechanism.
Xinxing Ren, Qianbo Zang, Ziyan Wang et al.· 0 citations
AgentRewind is presented, a runtime recovery framework that records aligned checkpoints of the agent context and controlled environment, allowing agents to return to an earlier state and resume execution with information from previous attempts, improving task success rate and average checklist progress over the compared baselines.
Yu Zhuang, Kefei Chen, Yitong Duan et al.· 2 citations
This work presents PhyAgentOS, a runtime foundation delivering scheduling, verification, memory, benchmarking, and safety as system-level services, and distinguishes execution termination from semantic task completion via evidence-grounded verdicts of success, failure, or replan.
Yang Liu, Weixing Chen, Xinshuai Song et al.· 2 citations
LLM agents increasingly take on long-running tasks whose history grows far beyond a single model context window. Existing approaches compress earlier interactions or extract selected information into fixed memory representations, committing to what to preserve before future needs are known. We present Scroll, a context manager that treats each agent session as an executable Session Environment. The environment is backed by an append-only Event Log and a sandboxed, persistent Python kernel. The kernel maintains a typed namespace across model calls, allowing tool outputs, retrieved history, and derived state to be bound to variables rather than serialized into the prompt at each call. Model-written code searches, materializes, and transforms session state through exec; only explicitly printed projections enter the model's working view for the next call. Context management thus becomes a programming task that inherits the improving coding abilities of LLMs, while the Event Log preserves lossless historical ground truth. As the working view approaches its budget, stale spans are evicted but remain recoverable: an eviction index keeps compact landmarks tied to exact Event Log addresses, so that the agent navigates directly to evicted regions instead of searching the full log. With Qwen3.8-Max as the backbone, Scroll achieves 94.8% on LongMemEval_S; 73.1% on BEAM_10M, surpassing the best published memory system by 5.1 points; and 86.7% on LOCA_256K, exceeding the best published long-horizon agent by 37.4 points.
Results show that long-horizon software development can be organized around a persistent project rather than a persistent agent, and EvoX Genesis is introduced, which instead makes the software project persistent while allowing local agents to remain finite-lived.
Beichen Huang, Zhenyu Liang, Bowen Zheng et al.· 0 citations
LocalLSTC is introduced, a training-free architecture that organizes control by temporal scope, maintaining persistent cross-step state to guide short-term execution commitments, and identifies temporal organization of control information as a distinct architectural dimension for locally deployed GUI agents.
