Point artifact publishing at a local directory and it writes files there instead of calling the service.
What's wrong with this entry?
Setting CLAUDE_CODE_EVAL_ARTIFACT_STUB_DIR makes artifact publishing write to that directory rather than contacting the artifact service, producing an index.html, a files/ folder for supporting files and a manifest.json, and returning a synthetic URL with version "1".
- Supporting file paths that escape the target directory, including via symlink, are skipped with a warning.
- In this path, payloads named
*.workshop.htmlare run through the structural verifier and refused, listing up to 12 violations. - The plugin-eval harness sets the variable for the sessions it spawns.
CLAUDE_CODE_EVAL_ARTIFACT_STUB_DIR
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.235
plugin evalnow tells you when a nearby plugin is not being loadedBoth mention eval
-
v2.1.235
--eval-diron the eval command, with warnings that name the fixBoth mention eval
-
v2.1.235
Eval setup refuses directories it cannot vouch for
Both mention eval