Agent libOS: A Runtime Substrate for Capability-Controlled Self-Evolving LLM Agents
arXiv:2606. 03895v2 Announce Type: replace-cross Abstract: Large language model (LLM) agents are becoming long-running software actors rather than fixed tool users.
arXiv:2609. 00546v1 Announce Type: cross Abstract: Agent systems are commonly described by the model and harness that currently produce their behavior.
arXiv:2606. 03895v2 Announce Type: replace-cross Abstract: Large language model (LLM) agents are becoming long-running software actors rather than fixed tool users.
arXiv:2604. 13097v3 Announce Type: replace-cross Abstract: Embodied agents increasingly rely on modular capabilities that are installed, upgraded, composed, and governed at runtime, yet the interfaces between these modules are specified only at the level of message types, so integration failures surface only during execution.
arXiv:2608. 11632v1 Announce Type: cross Abstract: Persistent AI agents accumulate versioned state across long horizons, but storage retention alone does not identify authoritative state.
arXiv:2608. 03836v1 Announce Type: new Abstract: A framework that persists execution state so a run can be interrupted, survive a crash, and continue must decide what a resume means for effects that already fired.
arXiv:2607. 10487v1 Announce Type: cross Abstract: LLM agents can commit durable effects from authority evidence that was valid earlier in execution: a DOM snapshot, approval epoch, version witness, branch token, or worker result.
arXiv:2606. 22504v1 Announce Type: cross Abstract: Coding agents often receive broad tool access for an entire task, even when a resource is needed only for one subgoal.
arXiv:2610.15991v1 Announce Type: new Abstract: Distributed agent workflows cache delegated authority at tool gateways. Revocation may be reported at issuer commit, transport acknowledgment, or recei...
arXiv:2609.21284v1 Announce Type: cross Abstract: Long-running AI agents outlive initiating processes through credentials, delegated tasks, queues, callbacks, reservations, and provider-side operatio...
arXiv:2608.28553v4 Announce Type: replace Abstract: Plugin-based agents assemble capabilities at runtime, and the spatiotemporal-composability calculus proves a reversibility guarantee for this assem...
arXiv:2607. 09493v1 Announce Type: new Abstract: Agentic LLM systems that generate code through multi-turn tool use face a fundamental context problem: each session starts from zero, discarding the configuration choices, domain constraints, data schemas, and tool-use patterns that made previous sessions productive.
The paper introduces "authorization succession," a framework that preserves authority across self‑modifying AI agent populations that can replace, fork, or roll back. It defines a protocol binding each generation to a manifest, root, unique parent, lineage, and population sequence, and establishes invariants that control root‑lifetime consumption and population exposure. The authors prove properties such as population‑safe succession, fork conservation, and rollback non‑reminting, and validate the approach with an executable evaluation covering 32 decisions and external adapters for two mutation systems.
The paper introduces Persona‑Execution Separation (PES), an architecture pattern that splits an LLM agent’s persona—its instructions, tone, and self‑presentation—from its execution—stateful, auditable work—by placing them in distinct trust domains linked through a governed contract bridge. PES allows the persona to evolve freely while keeping execution traceable, using mechanisms such as an approval matrix, data‑loss‑prevention exceptions, and continuous identity. A pilot implementation on a regulated digital‑employee platform demonstrated that PES successfully decouples persona drift from execution audit, preventing re‑validation or fingerprinting of hard‑asserted fields.