{"version":"2.1.269","anchor":"artifact-read-output-marks-content-authored-by-others-more","canonical_anchor":"artifact-read-output-marks-content-authored-by-others-more","heading":"Artifact reads now flag more content as untrusted with a clearer warning","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/artifact-read-output-marks-content-authored-by-others-more","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Artifact reads now flag more content as untrusted with a clearer warning\n\nReading an artifact now detects more cases of untrusted or co-written content and prepends a warning to the summary\n\n**What**\n\nWhen Claude Code reads a published artifact file, it now does more work to figure out whether the content should be treated as untrusted or co-authored data, and warns about it more consistently:\n\n- It detects whether the artifact is a recognized app type, or an HTML page containing a `ws-decisions` marker, and uses either signal to prepend a `contentLead` warning string to the returned or summarized text.\n\n- The check for marking content as \"authored by others\" (untrusted or co-written) now also triggers on a new `authoredByOthers` field or a new internal condition, in addition to the previous checks (`cowritten`, `typeLocked`, or Slack-origin content).\n\n- The new `contentLead` string is now prepended across several of the read-result templates, not just one.\n\n**Why**\n\nThis makes it more likely that content written or generated outside the current session (by another tool, another app, or another author) is clearly labeled as such when Claude reads it back, reducing the chance that Claude treats untrusted or externally-authored artifact content as if it were its own prior output.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}