{"version":"2.1.275","anchor":"cross-organization-artifact-reads-now-tracked-and-flagged-as","canonical_anchor":"cross-organization-artifact-reads-now-tracked-and-flagged-as","heading":"Cross-organization artifact reads now tracked and flagged as untrusted input","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/cross-organization-artifact-reads-now-tracked-and-flagged-as","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Cross-organization artifact reads now tracked and flagged as untrusted input\n\nContent read from another organization's artifact is now explicitly flagged as untrusted\n\n**What**\n\nClaude Code now tracks, per tool use, whether the user has consented to reading artifacts belonging to another organization. When content from such an artifact (either shared directly from another organization, or a public artifact from outside the user's organization) is included, it's now given an explicit warning label instructing that it be treated as untrusted input.\n\n**Why**\n\nThis reduces the risk of content from outside an organization being treated as trustworthy instructions or data by default, similar to how other external content is already handled.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}