What
When 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:
- 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
- Successful file-list results for public artifacts now carry additional fields marking them as public and possibly narrowed in scope
- 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
Why
This 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.