{"version":"2.1.242","anchor":"listing-and-describing-artifact-types-no-longer-asks-permiss","canonical_anchor":"listing-and-describing-artifact-types-no-longer-asks-permiss","heading":"Listing and describing artifact types no longer asks permission, and listing can be filtered","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/listing-and-describing-artifact-types-no-longer-asks-permiss","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Listing and describing artifact types no longer asks permission, and listing can be filtered\n\nListing and describing artifact types no longer prompts, and listing takes a filter.\n\n**What**\n\nListing the published artifact types available to you and describing one are now treated as read-only and skip the permission prompt with a stated reason. Listing gained a text filter, capped at 200 characters. Creating an artifact type in the cloud is still off: it needs `CLAUDE_CODE_ARTIFACT_TYPE_CLOUD_CREATE` or a remote-config gate whose built-in fallback is false.\n\n**Evidence**\n\n`Listing the published Artifact types available to the user is a read-only action`\n\n- Area: Artifacts\n- Names: `CLAUDE_CODE_ARTIFACT_TYPE_CLOUD_CREATE`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}