Recoverability and Verifier Strength: Two Measured Preconditions for Unattended Agent Self-Improvement
Organizations: Uniphore
Abstract
Agent platforms are starting to improve their own agents: they read a deployed agent's execution traces, derive a change, have an automated verifier approve it, and release it with no human author. How much of this loop can safely run without a human? We propose two quantities a platform can measure. Verifier strength is how well the available verifier -- often an LLM judge -- agrees with a trusted reference verifier; it limits how much a step can improve the agent. Recoverability is how cheaply a bad change can be undone: whether undoing it needs a new verifier approval, and how much of the old behavior a rollback restores. A step should run unattended only if both are adequate. On our platform this rule allows prompt, tool and skill edits to run unattended and keeps weight updates under human sign-off. Our main contribution is these two definitions and how to measure them. We built a platform that applies the rule and tested it in two ways: on the platform's own approval gate, and in controlled experiments on the -bench agent benchmark. On verifier strength, the platform's LLM judge sometimes gave the same score no matter what it was shown (9 of 37 settings) and reported no error, so a verifier can look healthy while approving anything; its strength must be measured, and two simple tests catch the failure. On recoverability, restoring a saved copy brought the agent back to its original behavior, but a regenerated undo did not, so only changes whose old version is kept can be reversed without a human; and while a change was deployed, it altered the outcome of 17 percent of tasks beyond normal run-to-run variation, which no undo repairs. Together these support the rule: a change can run unattended only when its old version is kept and its verifier's strength has been measured.
Figures & tables
| Precondition | Finding | Implication for unattended changes |
|---|---|---|
| Verifier strength | Platform’s LLM gate gave a constant in 9/37 settings, no error (§ 5.1 ) | A gate can look healthy while approving anything: measure |
| Verifier strength | Weaker verifiers picked worse changes; not significant at 20 tasks (A2) | must be calibrated per platform (App. E ) |
| Recoverability | Saved copy restores exactly; regenerated undo does not (B) | Only changes with can be undone without a human |
| Recoverability | A deployed change altered of tasks beyond noise (B) | Undoing a change does not repair what it already did |
Appendix figures & tables3 assets
Supplementary material from the paper’s appendix.
Appendix
| largest-seed share | ||||||
|---|---|---|---|---|---|---|
| .33/.17 | .50 | .67 | .83/.79 | |||
| breadth 3 | deployed | 0.250 | 0.250 | 0.250 | 0.250 | — |
| no-signal | 0.250 | 0.250 | 0.250 | 0.250 | — | |
| threshold | 0.250 | 0.100 | 0.100 | 0.090 | ||
| breadth 6 | deployed | 0.938 | 0.506 | 0.445 | 0.371 | |
| no-signal | 0.842 | 0.803 | 0.891 | 0.832 | ||
| batch | what varies | settings | calls |
|---|---|---|---|
| A | imbalance judge model, breadth 3 and 6 | 24 | 240 |
| B | imbalance prompt variant, breadth 3 and 6 | 32 | 320 |
| C | imbalance how the score is requested | 24 | 238 |
| R | repeat of one dataset pair | 24 | 240 |
| S | imbalance breadth , two agents | 68 | 680 |
| total | 172 | 1,718 |
| dimension | how it is undone | are its side effects undone? | |
|---|---|---|---|
| system prompt | write back previous value | 0 | no: answers already served |
| tool definitions | write back previous value | 0 | no: calls already made |
| skills | write back previous value | 0 | no: answers already served |
| model weights | re-pin previous adapter | 0 | no: answers already served |
LLM Agent Self-Improvement
Large language model agent self-improvement studies how agents use experience and feedback to improve their behavior, tools, and workflows.
See all 273 papers