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.227 Home All releases ←olderv2.1.226 v2.1.228newer→
Claude Code v2.1.227

Artifact tool can resolve comment threads, behind an off-by-default flag

Not switched on
Useful2 Signal4
Artifacts Notable not in their notes

Claude could mark a comment thread on a published artifact as resolved, but the path is off.

A resolve action for artifact comment threads exists behind CLAUDE_CODE_ARTIFACT_COMMENTS, off by default.

Feature flag
tengu_teal_corbel On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

This account: on · anonymous baseline: on · compiled default in v2.1.227: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.227. It isn't a statement about your account. What a flag value here can and cannot tell you

CLAUDE_CODE_ARTIFACT_COMMENTS
What

The Artifact tool gains a resolve action alongside comments and reply, marking one comment thread on a published artifact as resolved. It is only offered when artifact comments are enabled, via CLAUDE_CODE_ARTIFACT_COMMENTS or the tengu_teal_corbel remote flag, which falls back to off, so nothing in this build turns it on by itself.

Details
  • thread_id is required and must be a lowercase UUID taken from the comments action; a missing one errors with "thread_id required for action \"resolve\"".
  • Success reads "Marked comment thread ... resolved. Viewers see it as resolved by Claude; a person can reopen it." Failures separate not-authorized, where only the thread starter or a writer of the artifact may resolve, from Claude not being activated on the thread.
  • Plan mode never mutates comment-thread state, so the action is refused there.
  • Guidance tells Claude to reply and then resolve only threads it actually addressed, and never to re-resolve an already-resolved thread.
Evidence

thread_id must be a thread id from action "comments" (a lowercase UUID), 'thread_id required for action "resolve"', Plan mode never mutates comment-thread state, thread_id required for action "resolve", 'thread_id applies only to actions "comments", "reply", and "resolve", and text only to "reply"'

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.227 →