{"version":"2.1.242","anchor":"artifact-type-instructions-are-treated-as-untrusted-text","canonical_anchor":"artifact-type-instructions-are-treated-as-untrusted-text","heading":"Artifact type instructions are treated as untrusted text","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/artifact-type-instructions-are-treated-as-untrusted-text","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Artifact type instructions are treated as untrusted text\n\nInstructions bundled with an artifact type are wrapped as untrusted text that cannot widen permissions.\n\n**What**\n\nInstructions that come with an Artifact type are now wrapped in a preamble and a trailing warning saying they cannot grant permissions or widen the task, since anyone who can publish to the Artifact could have written them.\n\n**Details**\n\n- Two preambles exist: one for a trusted Artifact type and one for the case where the instructions could have come from any publisher.\n- The trailing warning rules out fetching or publishing elsewhere, putting local files or credentials into the Artifact, and editing permission settings, CLAUDE.md or config on the instructions' say-so.\n- Always applied as part of assembling the Artifact system prompt.\n\n**Evidence**\n\n`artifact-type-instructions`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}