arXiv AI
Recoverability as a System Primitive for Long-Horizon AI Agents
Read the original on arXiv AI →The Flow has not summarised this story yet — read it at arXiv AI.
Related stories
arXiv AI
Sep 1
Safe to Resume? Breaking Execution Continuity of Agent Execution via Rollback
arXiv:2608.29381v1 Announce Type: cross Abstract: AI agents are moving toward persistent, stateful execution across various applications, accumulating execution state and external effects that are co...
Hugging Face Trending Papers
Jun 29
Always-OnAgents:A Survey of Persistent Memory, State, and Governance in LLMAgents
Always-on agents are systems whose future behavior depends on durable state accumulated across earlier interactions. We treat them as persistent-state systems: the operative system includes retrievable memories, but also task ledgers, permissions, credentials, commitments, provenance and audit records, shared state, trigger conditions, and externally committed effects linked to those records.
arXiv AI
Aug 5
Designing for Doubt: The Case for Informed Abstention in Autonomous Agents
arXiv:2606. 02965v2 Announce Type: replace Abstract: As large language models gain tool access and are deployed as autonomous agents capable of editing records, executing transactions, and modifying infrastructure, we still evaluate them based on the sole metric of task completion.
arXiv AI
Jun 30
Always-OnAgents:A Survey of Persistent Memory, State, and Governance in LLMAgents
arXiv:2606. 30306v1 Announce Type: cross Abstract: Always-on agents are systems whose future behavior depends on durable state accumulated across earlier interactions.
arXiv AI
Aug 17
AgentRewind: Recoverable Execution for Long-Horizon LLM Agents
arXiv:2608. 14380v1 Announce Type: new Abstract: Many real-world tasks require LLM agents to interact with their environments over long execution horizons.
arXiv AI
Aug 26
Rebuild Dossier: Mechanically-Enforced Specs for Agentic App Rebuilds, and What Model-Tier Failures Reveal
The paper introduces rebuild‑dossier, an open‑source tool that locks an application’s real interface before code is written and enforces one‑test‑at‑a‑time building through automated checks. In experiments, a compliant agent failed a held‑back test while a rule‑breaking agent passed, showing that a passing test suite can be gamed. The study also demonstrates that the automated check mechanism, rather than interface‑locking alone, is crucial for reliable rebuilds, and that multi‑level verification catches errors that single‑level checks miss.