{"version":"2.1.295","anchor":"artifact-read-consent-gate-no-longer-depends-on-a-feature-ch","canonical_anchor":"artifact-read-consent-gate-no-longer-depends-on-a-feature-ch","heading":"Artifact read consent and comment checks now always apply","tier":"notice","area":"Artifacts","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/artifact-read-consent-gate-no-longer-depends-on-a-feature-ch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Artifact read consent and comment checks now always apply\n\nForeign artifact reads now always need consent, and reading comments always loads and checks the artifact first\n\n**What**\n\nTwo artifact permission checks no longer depend on an internal switch and now always run:\n\n- Reads that Claude Code treats as foreign always need your consent.\n\n- Reading an artifact's comments always loads and checks that artifact first, as a limited read of one named artifact.\n\n**Why**\n\nThese consent checks used to apply only in some cases and are now standard, so expect a consent request whenever Claude reads a foreign artifact.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}