3 people reported
All time, since Sep 28.
Shared artifacts unreadable
“Claude Code can't read a colleague's Claude Docs artifact that the session's own claude.ai account opens fine in the browser.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/claude-code/issues/936/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Shared artifacts unreadable from Claude Code but open in browser. Docs connector read denies access and Artifact tool read returns only the viewer shell, with none of the document's text.
Is this your bug?
File my report- Where
- Artifact tool
- Error text
{"verdict":"deny","reason":"access"}- Versions
- 2.1.280 to 2.1.294
- Platforms
- macOS
- How bad
- Breaks a normal workflow.
Not quite your bug?
- Artifact read consent blocks4 people
Original reports3, newest first
- Shared artifact not accessible via Claude Code API, but accessible in browser#100588
- Can't read a Claude Docs artifact my account can view: Docs connector denies read, Artifact read returns only the viewer shell#97962
- Can't read a Claude Docs artifact my account can view: Docs connector denies read, Artifact read returns only the viewer shell#97960