Rank, 14 days: 50 on the Claude Code sheet
4 people reported
All time, since Sep 29, including 2 thumbs-up on GitHub.
Artifact read consent blocks
“An artifact shared directly with the Claude Code account, by name, still cannot be read by an unattended agent on that account.”
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/1065/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
Artifact read of another account's artifact blocks on unanswerable consent prompt. Artifact read stops at "was made by someone else. Let Claude read it?" with "No one can answer in this session", including shared and public artifacts.
Is this your bug?
File my report- Where
- Artifact tool
- Error text
Nothing was done. This needs a yes to: "Liturgy Planner: verses, repeating rows" was made by someone else. Let Claude read it for the rest of this conversation? No one can answer in this session.- Versions
- 2.1.314
- Platforms
- Linux
- How bad
- Breaks a normal workflow.
Not quite your bug?
- Shared artifacts unreadable3 people
Original reports3, newest first
- Artifact tool: an artifact shared directly with the Claude Code account still needs a human to press yes in every session before an agent on that account can read it#106333
- Artifact tool: an artifact shared with anyone with the link still needs a human to press yes in every session, so unattended agents cannot read public canvases#106332
- Cloud session parks forever on an Artifact read consent prompt that cannot reach a user#98304