{"version":"2.1.234","anchor":"eval-runs-can-publish-artifacts-to-a-local-directory-instead","canonical_anchor":"eval-runs-can-publish-artifacts-to-a-local-directory-instead","heading":"Eval runs can publish artifacts to a local directory instead of the service","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/eval-runs-can-publish-artifacts-to-a-local-directory-instead","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Eval runs can publish artifacts to a local directory instead of the service\n\nPoint artifact publishing at a local directory and it writes files there instead of calling the service.\n\n**What**\n\nSetting `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\".\n\n**Details**\n\n- Supporting file paths that escape the target directory, including via symlink, are skipped with a warning.\n- In this path, payloads named `*.workshop.html` are run through the structural verifier and refused, listing up to 12 violations.\n- The plugin-eval harness sets the variable for the sessions it spawns.\n\n**Evidence**\n\n`CLAUDE_CODE_EVAL_ARTIFACT_STUB_DIR`\n\n- Area: Artifacts\n- Names: `CLAUDE_CODE_EVAL_ARTIFACT_STUB_DIR`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 3\/5"}