Artifacts: a shared artifact is unreachable without the link (add a "Shared With Me" view)

What happens

An artifact published from Claude Code and then shared, either organization-wide or to a specific person, does not appear anywhere in the recipient's Artifacts gallery at claude.ai/code/artifacts. That view lists only artifacts the viewer created. There is no "Shared With Me" tab or filter, so the only way a recipient can reach a shared artifact is a link somebody sends them separately.

Steps to reproduce

1. Publish an artifact from Claude Code as account A.
2. Share it from the page's share menu, setting General access to everyone in the organization, "Can view".
3. As account B in the same organization, open claude.ai/code/artifacts.

Expected: the shared artifact is discoverable somewhere in that view.

Actual: it is not listed. Account B sees only artifacts they created themselves.

Also tried, to rule out the obvious explanations

• Account B opened the artifact successfully from a direct link, so access really had been granted.
• Adding account B explicitly as an Editor, on top of the organization-wide share. Still not listed.
• Fully quitting and reopening Claude after access was granted. Still not listed.

So this is not a permission-level problem and not a stale-cache problem. It appears to be the documented behavior, which is why this is a feature request rather than a bug report.

Why it matters

Sharing implies findability. A team that shares an artifact reasonably expects the recipients to be able to find it again later, and at the moment the link is the only handle on it. If a recipient loses the message that carried the link, the artifact is effectively gone for them even though they still have permission to view it.

It also rules artifacts out for anything a team comes back to, such as a reference page or an index, because a shared artifact can never be easier to find than the message that delivered its URL.

Request

A "Shared With Me" tab or filter in the Artifacts view, listing artifacts shared with the signed-in user, whether they were shared individually or organization-wide.

One related note: listing artifacts programmatically has the same limitation, and the response text acknowledges it, saying that artifacts shared organization-wide which the user has not opened may not appear. A recipient-side listing would make both surfaces consistent.