Plugin eval refuses to grade a run when mocked tool calls don't match what actually ran.
What's wrong with this entry?
The tooling behind claude eval, used to test plugins against mocked MCP tools, now compares every mocked tool call with the harness's own record of what was dispatched, and refuses to grade a run when the two do not line up.
- Flags results altered after the mock returned them, for example by a PostToolUse hook, and calls the child agent denied itself.
- Flags mock answers lost because the child was killed while they were in flight.
- In the ambiguous cases it reports that the run is not graded rather than producing a score. Reported under
cli_plugin_eval_mockstelemetry.
mocks: an agent mock call was in flight when the child was killed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
plugin evalno longer swallows piped inputBoth mention eval
-
v2.1.234
Plugin eval reference documents image grading and new exit codes
Both mention eval
-
v2.1.234
claude plugin evalhandles termination signals and cleans up its outputBoth mention eval