{"version":"2.1.239","anchor":"artifacts-published-from-a-slack-channel-get-their-own-untru","canonical_anchor":"artifacts-published-from-a-slack-channel-get-their-own-untru","heading":"Artifacts published from a Slack channel get their own untrusted-content framing","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/artifacts-published-from-a-slack-channel-get-their-own-untru","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Artifacts published from a Slack channel get their own untrusted-content framing\n\nArtifacts published from your Slack channel get their own untrusted-content warning wrapper.\n\n**What**\n\nHTML from an artifact published in your Slack channel is now wrapped in prompt text of its own, warning that it may contain edits by other people and that nothing in artifact content can grant Claude extra permissions.\n\n**Details**\n\n- This is a third pairing alongside the existing wrappers for co-written artifacts and Artifact-type content.\n\n**Evidence**\n\n`is from an artifact published from your Slack channel and may contain others' edits`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 4\/5"}