Eval tooling can adopt recorded mock responses into a checksummed replay directory.
What's wrong with this entry?
Internal eval tooling can now take newly recorded MCP mock server responses from a run and adopt them into a .replay/ directory, with a manifest file and per-file sha256 hashes so a copy can be checked, and guards against another process writing at the same time.
- Developer and eval tooling only; nothing here is reachable from a normal session.
Each line carries the sha256 of the file as written; check the copy you take against the hash printed to the terminal
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