{"version":"2.1.265","anchor":"new-pre-write-consent-check-when-creating-artifact-type-inst","canonical_anchor":"new-pre-write-consent-check-when-creating-artifact-type-inst","heading":"New pre-write consent check when creating artifact-type instances","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-pre-write-consent-check-when-creating-artifact-type-inst","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### New pre-write consent check when creating artifact-type instances\n\nCreating a private artifact type now runs an extra permission check before asking you to approve it\n\n**What**\n\nBefore Claude Code asks you to approve creating a new private artifact from a type, it now runs an additional check first. This check consults a permission-ruling helper tagged `type_create`, and if that ruling says the action should be confirmed with you (and it hasn't already been remembered as approved for that type and slug), Claude Code returns a 'read' action instead of going straight to the create-artifact approval prompt.\n\n**Why**\n\nThis adds an extra layer of permission checking before creating a new artifact type, potentially changing what prompt or action you see compared to going straight to a create-artifact approval request.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}