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.251 ·

Clearer rules for activating and resolving comment threads

Claude now explains how to activate an artifact comment thread it cannot resolve.

You'll notice Improvements
JSON All of v2.1.251
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.251,
ImprovementsSection of the release
What

Guidance on artifact comment threads changed. A thread is activated by replying with Send to Claude or by mentioning @claude, and when Claude cannot resolve a thread that was never activated it must leave it open and tell you that a writer can send it to Claude or resolve it in the artifact view. The old wording just told Claude to leave the thread for the commenter.

Evidence

reply on it with Send to Claude

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

Read from
Names in the bundle@claude
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up @claude, on All settings. * **Type**: array of objects, each with `marketplace` and `plugin` strings. An entry can instead be a `"plugin@marketplace"` string such as `"telegram@claude-plugins-official"`, which Claude Code treats as the equivalent object. The string… settings-reference see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up @claude, on All settings.

See this entry in the whole of v2.1.251 →

Feedback