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
Vercel Board: A Message Board Built for Agent Swarms
0dev.to

GTA VI: 212 GB, Pre-Load and What Take-Two Says About AI
0dev.to

Discord bot offline a week while systemd said active: a plugin timeout
0dev.to
Your AI Bill Has a Second Price Dial — and It Can Out-Swing Model Choice
0dev.to
Bitbucket Data Center Counts Point to a Repository Service With a Separate Admin Boundary
0dev.to

pgvector HNSW Filtering: 431 of 2,000 LIMIT 10 Queries Came Back Short
0dev.to