{"version":"2.1.239","anchor":"saving-artifact-files-outside-the-scratchpad-now-needs-a-per","canonical_anchor":"saving-artifact-files-outside-the-scratchpad-now-needs-a-per","heading":"Saving artifact files outside the scratchpad now needs a person","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/saving-artifact-files-outside-the-scratchpad-now-needs-a-per","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Saving artifact files outside the scratchpad now needs a person\n\nSaving artifact files outside the scratchpad now needs a human, not the automatic approver.\n\n**What**\n\nWhen Claude saves a file it fetched from an artifact to a path outside the session scratchpad, or inside it under a name the file-edit safety rules watch (git, hook, tool or agent configuration), the approval can no longer be granted by the automatic permission classifier. A human has to approve it.\n\n**Details**\n\n- The stated reason is that both the path and the contents were chosen by whoever wrote the artifact, not by you.\n- Ordinary saves to unremarkable names inside the scratchpad are unaffected.\n\n**Evidence**\n\n`writes a file outside the session scratchpad, where the project's tools may act on it, with a path and contents chosen by a writer of the artifact \\u2014 approval must come from the user, not the auto-permission classifier`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}