Sign inGet started
Paper · arXiv

RetryBench: Separating Retry Permission from Recovery Outcomes in GPT Tool Use

False retry permission (FRP) occurs when an agent retries a timed-out tool call without support from the visible contract. RetryBench separates this error from realized recovery. Successful protected recovery does not imply reliable rejection of unsupported retries. In a 720-response key control, valid keys usually enabled safe progress, but offered changed keys elicited unsupported retries in Sol (1/80), Terra (55/80), and Luna (60/80). A later 240-response control removed the candidate and required models to supply a key. Luna still made 8/80 unsupported dispatches; Sol and Terra made none in 80 responses each. Accepting a displayed bad key therefore cannot explain all observed errors, ...

AuthorsYou Liu, Yue Liu, Quanchao Lu
Primary categorycs.AI
Published11 October 2026
Last updated at source11 October 2026
cs.AIcs.CR
Embed this entry
<iframe src="https://silytics.si/embed/item/12d5006d-119a-4dc3-97ea-f34506541962" width="420" height="190" style="border:0" loading="lazy" title="Silytics entry"></iframe>

Free, no tracking. More about feeds and embeds.

Silytics shows public metadata from arXiv and links to the original. Information may be incomplete or out of date. Last refreshed 14 October 2026. Licenses and terms of the original apply to the work itself. Not financial, legal or professional advice.