Artifact comments silently dropped: UI confirms sent, comment never reaches the session
Commenting on a published artifact from a Claude Code session shows a sent confirmation, but the comment never arrives in the conversation. The assistant receives the accompanying message with no comment attached and no anchor. Reproduced twice, minutes apart.
Environment: Claude Code 2.1.260, Linux 6.8.0-90-generic. Artifact published from the CLI session.
Steps:
- Publish an HTML artifact from a CLI session
- Open it at its claude.ai/code/artifact/<uuid> URL
- Select text in the rendered page, add a comment
- UI confirms it as sent
- Send any message in the session
Expected, per https://claude.com/docs/claude-science/comments end it. Pending comments appear above the message box and aresent with your next message." The comment and its anchor should arrive with that message.
Actual: the message arrives with no comment and no anchor. Theit as plain text, which loses the selection that madecommenting useful.
Notes: the commenting capability is present in the artifact runtime - the published page's frame preamble lists a comments module. Comments load dynamically, so fetching the artifact HTML does not surface ththis flow for the web app; if it is not supported forCLI-published artifacts, the UI should not report the comment
Impact: the failure is silent and confirmed-positive. The user believes they have communicated something anchored and specific; the session proceeds without it and neither side can tell.