{"version":"2.1.274","anchor":"artifact-comment-read-errors-now-carry-structured-more-spec","canonical_anchor":"artifact-comment-read-errors-now-carry-structured-more-spec","heading":"Artifact comment-read errors now carry structured, more specific explanations","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/artifact-comment-read-errors-now-carry-structured-more-spec","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Artifact comment-read errors now carry structured, more specific explanations\n\nArtifact comment-read failures now show specific reasons instead of one generic error\n\n**What**\n\nWhen Claude Code can't read comments on an artifact (a shared document or file created in a conversation), it now explains why in more detail. A new internal helper translates specific failure reasons, such as the artifact belonging to another organization, not being a shared link, not currently being served, being blocked by a permission rule, having a pending notice, or a check failing, into a plain-language explanation plus a suggested next step (like saying so, making your own calls, or listing available items).\n\n**Why**\n\nPreviously all these situations produced the same generic \"its sharing could not be checked\" message. Now you get a more specific reason and a hint about what to try next, making it easier to understand why an artifact comment couldn't be read.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}