arXiv (All)
open access
Where Does Exactly-Once Live? Model, Harness, and Tool-Contract Effects on Duplicate Side Effects in LLM Agents
When a tool-using agent's write times out or returns a server error, the action may already have taken effect. Retrying blindly duplicates it -- a second charge, a second announcement, a second deployment -- while giving up skips required work. We ask where exactly-once behaviour should be enforced:
Conceptio Open Archive
Analyze & explore related research in Conceptio
Connect this record directly into your research workflow or AI agent. Explore citations across open repositories, query full text, and export structured proof bundles.
This document is indexed with metadata only: full text is not available in the archive for this record. Open the official source ↗
Related documents
- RepoRescue: An Empirical Study of LLM Agents on Whole-Repository Compatibility Rescue#329145
- Facts Without Rules: Boundary Metadata Collapse in Multi-Agent LLM Handoffs#793252
- Facts Without Rules: Boundary Metadata Collapse in Multi-Agent LLM Handoffs#789248
- AI Agent Pull Requests on GitHub: Frequency, Structure, and Merge Conflict Rates#343545
- Invalidation Contracts for Cross-Episode Agent Memory#819701
Record · ID 1077024
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Bring this data into your agent: Connect via MCP or API · 20 free credits to start · no card required
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive