LLM agents often solve related requests from scratch, repeating the same planning and tool-use decisions. RECAP turns prior executions into structured, executable plans that can be retrieved, replayed, or used to guide a smaller agent on a new request.
The reusable unit is an ordered sequence of successful tool calls, with their goals and arguments. Reuse produces fresh tool observations, allowing the system to respond to changed inputs and external state.
7,797benchmark questions |
3tool-use sources |
2agent architectures |
Capture → Compile → Retrieve → Judge → Execute
| Retrieved plan | Execution path |
|---|---|
| Full match with replay-compatible arguments | Re-execute the stored tool sequence and derive an answer from fresh outputs. |
| Partial match or adaptation required | Give the structured plan to a smaller agent as a concrete demonstration. |
| No applicable plan | Run the larger agent and compile an eligible execution into a new plan. |
When can an agent safely reuse prior work? REUSE-QA studies this question through groups of related tool-use requests whose wording, inputs, or conditions change.
The benchmark contains 2,627 original questions and 5,170 human-verified variants, built from FinanceBench, GAIA, and SQL-API-Bench.
| Source | Original questions | Variants | Total |
|---|---|---|---|
| FinanceBench | 150 | 303 | 453 |
| GAIA · Levels 1–2 | 139 | 179 | 318 |
| SQL-API-Bench | 2,338 | 4,688 | 7,026 |
| Total | 2,627 | 5,170 | 7,797 |
Three controlled variation types expose different reuse challenges:
Each evaluation starts with an empty plan library. Original questions precede their variants, and all methods receive the same ordered stream.