{"version":"2.1.265","anchor":"reading-a-first-party-artifacts-own-files-can-skip-approval","canonical_anchor":"reading-a-first-party-artifacts-own-files-can-skip-approval","heading":"Reading a first-party artifact's own files can now skip approval","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/reading-a-first-party-artifacts-own-files-can-skip-approval","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Reading a first-party artifact's own files can now skip approval\n\nReading files from a first-party artifact's own file cache no longer always requires approval, and its progress text now says 'read' instead of 'save'\n\n**What**\n\nReading files or assets from the user's own artifact can now be exempted from the usual approval prompt when the artifact was made from a published first-party Artifact type, with a new decision-reason message explaining why. There's also a shortcut for resources that were already read or approved earlier under a display name.\n\nThe user-facing progress text for these actions was also updated: the `read_file` action now shows \"read \" instead of \"save file \", and `read_asset` now shows \"read asset \" instead of \"save asset \". A destination arrow in the progress text is now suppressed when the resolved destination is a default directory.\n\n**Why**\n\nThese file-cache operations are reads, not writes, so treating them as reads both reduces unnecessary approval prompts for trusted first-party artifacts and makes the displayed action text accurately describe what's happening.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}