In confined evaluation runs, allow rules from settings files are ignored; only CLI ones count.
What's wrong with this entry?
With CLAUDE_CODE_EVAL_CONFINED set, file-read permission checks reject anything outside the set of paths the run was allowed to read, and always-allow rules are honoured only when they came from a command-line argument, so allow rules written in settings files are ignored.
- The denial text is
source outside the readable set in an evaluation run. - Both paths are off entirely when the variable is unset.
source outside the readable set in an evaluation run
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