Under the hood
Useful2 Signal3
Eval sandboxes get their own git config so they don't read your machine's setup.
What's wrong with this entry?
Anonymous. No account, no email.
What
Setting up an eval sandbox now records a separate operator config directory and writes its own shared git config, common-directory pointer and hooks directory, so evals do not read the surrounding machine's git setup. On macOS the sandbox uses prefixed temp paths under /tmp.
Details
- the temp path layout differs by platform; the config and hooks setup is unconditional
Evidence
operatorConfigDir: He()
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