Source Intelligence

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.238 Home All releases olderv2.1.237 v2.1.239newer
Claude Code v2.1.238

Claude will not resolve a comment thread it was not invited into

You'll notice
Useful3 Signal2
Artifacts

Claude will not resolve artifact comment threads it was not explicitly invited into.

What

In artifacts, resolving a comment thread now follows the same rule as replying: it only works on threads a person explicitly activated for Claude. Claude is told to report what it did and leave the thread for the commenter rather than resolving one marked as not activated, even if it addressed the feedback.

Details
  • The per-thread status line was reworded from "Claude replies: NOT activated" to spell out that Claude can neither reply nor resolve.
  • Applies only in sessions where the comment verbs are present in the tool schema.
  • Automatic-reply failures gained two more outcomes, a withheld full rewrite and a timeout, each with its own message posted to the thread and shown in the session.
  • Reply composition failures are now reported distinctly: truncated (with a flag for empty output), empty, and errored.
Evidence

Resolve, like reply, works only on threads activated for Claude, never call resolve on a thread marked NOT activated, Resolve, like reply, works only on threads activated for Claude: never call resolve on a thread marked NOT activated

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

See this entry in the whole of v2.1.238 →