Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

Artifact comment threads are summarised before Claude acts on them

Not switched on
Useful2 Signal4
Artifacts Notable not in their notes

Artifact comment threads get summarised so the permission prompt names what's being acted on.

Artifact comments need CLAUDE_CODE_ARTIFACT_COMMENTS or a server gate that falls back to false.

CLAUDE_CODE_ARTIFACT_COMMENTS
What

When Claude is asked to act on an artifact comment, new code reads the thread behind it and summarises the opening comment so the permission prompt can name what is being acted on. Artifact comments as a whole are off unless CLAUDE_CODE_ARTIFACT_COMMENTS is set or the server turns on the gate whose built-in fallback is false.

Details
  • The summary records the thread id, who opened it, an excerpt, the reply count and whether it is resolved.
  • Each comment is attributed as your own, Claude's, another viewer's, or unknown for artifact-posted and agent comments.
  • The read is bounded by a 4 second timeout; failures are reported as no opening comment, deadline or read threw.
  • Results are cached per artifact and thread, tied to the current tool call, trimmed to a fixed size and cleared when the signed-in account changes.
Evidence

artifact_comment_consent_read

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.248 →