Backend
Checking Retry Transparency in Agent Tools
arXiv cs.SE0 views
arXiv:2611.23307v1 Announce Type: new Abstract: A successful retry does not necessarily put the earlier attempt behind it. An old write may still overwrite a later acknowledged update; a partially executed file write may even empty a file after the retry has returned successfully. We study how to test the recovery guarantee behind an agent tool's local idempotence claim. Our prototype takes manually constructed, source-backed effect contracts and checks them at two levels: atomic retry-absorption obligations and bounded interleavings of successful-attempt microsteps. It emits model witnesses, conditional admission decisions, and explicit uncertainty when a completion boundary cannot be justified. The evaluation preserves a locally frozen purposive frame of 6 MCP components from 4 repositories; selected paths in 5 execute on the study machine and one backend remains unavailable. Real tests include file, graph, Git-index, document-update and browser bindings, together with a native Qdrant development matrix. In 27 missing-reply checks, the selective rule completes six justified workflows without an acknowledged goal violation, whereas strict coalescing completes none and blind retry completes nine with three violations. An intent-aware Porcupine specification independently agrees with all 156 complete-history oracles. These are mechanism-selected tests, not defect-prevalence estimates or a new linearizability algorithm. The contribution is an executable recovery-contract workflow that makes effect granularity, logical identity and completion assumptions testable rather than inheriting them from a tool annotation.
Source:https://arxiv.org/abs/2611.23307PreviousWhen Exact Inference Changes Code Selection: A Decision-Theoretic Analysis of B4NextRepository-Grounded Rubrics for Execution-Free Evaluation of Coding Agents
Related posts
Drawing 28 questions from an 84-question bank: how I score a deadly sins quiz
0dev.to
Count tokens before you call the LLM: tiktoken encodings, token budgets and chunking, with real numbers
0dev.to
![Quadruped Robot Software — Ch.10: Quadruped AI and Physical AI [KR]](https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffiibwtdu8wij6gnnuoyc.png)
Quadruped Robot Software — Ch.10: Quadruped AI and Physical AI [KR]
0dev.to
Signal #138: Java4Shell Hits AVX-512 JDKs; GPT-6.2 Astra and Sol Ship
0dev.to

Check Support Emails Before the LLM: Wolf Defender in Apache Camel
0dev.to

The Librarian, the Missing Book, and the AI with a Master Key. Sentinel IR MCP
0dev.to