{"version":"2.1.229","anchor":"listing-artifacts-no-longer-asks-for-permission","canonical_anchor":"listing-artifacts-no-longer-asks-for-permission","heading":"Listing artifacts no longer asks for permission","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/listing-artifacts-no-longer-asks-for-permission","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Listing artifacts no longer asks for permission\n\nListing artifacts no longer asks you for permission first.\n\n**What**\n\nThe Artifact tool's list action used to require a one-time confirmation per session, with separate prompts for the shared and all scopes. That branch is gone and listing is permitted outright as a read-only action in every scope.\n\n**Evidence**\n\n`Listing artifacts published by or shared with the user is a read-only action`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}