{"version":"2.1.265","anchor":"artifact-publish-root-validation-reworked-to-use-a-new-hel","canonical_anchor":"artifact-publish-sources-can-live-in-the-session-scratchpad","heading":"Artifact publish can now source files from the scratchpad","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/artifact-publish-root-validation-reworked-to-use-a-new-hel","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Artifact publish can now source files from the scratchpad\n\nArtifact publish's files\/root parameter can now point at the session scratchpad, not just the working directory\n\n**Unclear.** What the new options passed into the file-processing calls actually control is not stated.\n\n**What**\n\n- Sources for the artifact publish tool's `files` parameter (and the `root` it's relative to) can now live in the session's scratchpad directory, not only the current working directory \u2014 the tool's parameter descriptions were updated to say so explicitly.\n\n- The underlying trust check for the `root` parameter was reworked: instead of a manual string-prefix comparison against the working directory, it now calls a new helper pair to validate the path, and file-processing calls (both the general file-copy path and thumbnail generation) pass an extra options object from a new helper function.\n\n**Why**\n\nThis lets Claude publish artifacts built from files it created in its scratchpad, not just files in the project's working directory, while keeping the same path-trust safety checks, now reworked to also cover the scratchpad case.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}