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

Claude Code v2.1.227 ·

Comment threads report why they were not resolved

Failing to resolve an artifact thread now says whether you lacked permission or the thread was inactive.

Nothing to try yet In Development
JSON All of v2.1.227
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.227,
In DevelopmentSection of the release

Distinct resolve-refusal results exist only where artifact comments are enabled, which is not by default.

What

When resolving a discussion thread on an artifact, the result now distinguishes success from two refusals: the person asking is neither the thread starter nor a writer, or the thread was never activated. It appears only where artifact comments are available, which is not on by default in this build.

Evidence

not resolved (not the thread starter or a writer)

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

Feedback