Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.248 ·

Artifact comment threads are summarised before Claude acts on them

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

Nothing to try yet Notable No documentation found In Development
JSON All of v2.1.248
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.248,
What probably matters to youSection of the release

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

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.

Read from

See this entry in the whole of v2.1.248 →

Feedback