{"version":"2.1.248","anchor":"artifact-comment-threads-are-summarised-before-claude-acts-o","canonical_anchor":"artifact-comment-threads-are-summarised-before-claude-acts-o","heading":"Artifact comment threads are summarised before Claude acts on them","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/artifact-comment-threads-are-summarised-before-claude-acts-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Artifact comment threads are summarised before Claude acts on them\n\nArtifact comment threads get summarised so the permission prompt names what's being acted on.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- The summary records the thread id, who opened it, an excerpt, the reply count and whether it is resolved.\n- Each comment is attributed as your own, Claude's, another viewer's, or unknown for artifact-posted and agent comments.\n- The read is bounded by a 4 second timeout; failures are reported as no opening comment, deadline or read threw.\n- 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.\n\n**Evidence**\n\n`artifact_comment_consent_read`\n\n- Area: Artifacts\n- Names: `CLAUDE_CODE_ARTIFACT_COMMENTS`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}