{"version":"2.1.235","anchor":"artifact-asset-reads-clearer-refusal-and-public-reads-no-lo","canonical_anchor":"artifact-asset-reads-clearer-refusal-and-public-reads-no-lo","heading":"Artifact asset reads: clearer refusal and public reads no longer gated the same way","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/artifact-asset-reads-clearer-refusal-and-public-reads-no-lo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Artifact asset reads: clearer refusal and public reads no longer gated the same way\n\nArtifact asset-read refusal message now states where reads can run, and public reads use a separate gate check\n\n**Unclear.** What effect gatePublicRead:false has on which public reads are allowed is not stated beyond the flag being changed.\n\nThe refusal shown when the relay is unavailable for artifact asset reads was rewritten to state where asset reads can actually run: from a local session, or from an Anthropic-hosted cloud session with its gateway relay enabled, and that retrying elsewhere will not help. The access check is now called with `gatePublicRead: !1` (false), so the public-read path is no longer subject to the same gate as before. The environment check for this path also moved from an inline `CLAUDE_CODE_REMOTE` test to a shared helper.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}