{"version":"2.1.235","anchor":"artifact-asset-permission-scope-and-messages-reworded","canonical_anchor":"artifact-asset-permission-scope-and-messages-reworded","heading":"Artifact asset permission scope and messages reworded","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/artifact-asset-permission-scope-and-messages-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Artifact asset permission scope and messages reworded\n\nArtifact asset permission and error messages reworded, with broader scope and coverage\n\nApproving a read-only listing of an artifact's assets now also covers saving that artifact's assets locally for the rest of the conversation. The `read_asset` denial message was rewritten to distinguish a bad `asset_id` from an unresolvable `out_dir`, and the upload-target-changed error now also fires when `action` changes, not just when `url` changes.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}