Claude Code v2.1.225 ·
Replay harness reports exhausted cached calls
Internal replay testing now says which tool ran out of cached calls before failing.
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.225,
Internal ChangesSection of the release
What
A replayed tool call that runs past the end of the cached call list now records the mismatch before throwing.
Details
- The message is assembled from the position, tool name and count, ending in "... invoked but only N calls cached (exhausted)".
Evidence
calls cached (exhausted)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.225 →
