{"version":"2.1.274","anchor":"artifact-file-lists-can-now-be-read-for-public-artifacts-by","canonical_anchor":"artifact-file-lists-can-now-be-read-for-public-artifacts-by","heading":"Artifact file lists can now be read for public artifacts by non-org readers","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/artifact-file-lists-can-now-be-read-for-public-artifacts-by","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Artifact file lists can now be read for public artifacts by non-org readers\n\nPublic artifacts' file lists can now be read by people outside the owning organization, with clearer errors when they can't\n\n**What**\n\nWhen fetching the list of files inside an artifact (a piece of code or content Claude generates and shares), Claude Code now handles public artifacts differently:\n\n- If the artifact is publicly readable and the server declines to list files, the error now distinguishes a 'single_page' artifact (one with no separate file list) from a genuine refusal, where files simply aren't available to readers outside the artifact's organization\n\n- Successful file-list results for public artifacts now carry additional fields marking them as public and possibly narrowed in scope\n\n- A separate, distinct message now appears when a cloud-session artifact mount can't serve a specific file to an outside-org reader viewing a public artifact, rather than the generic 'no file published' message\n\n**Why**\n\nThis makes it clearer to someone outside an artifact's organization why a file listing or file fetch failed, rather than lumping every failure into one vague error.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}