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

Artifact comment errors distinguish missing thread from degraded fetch

Artifact comment errors now tell you whether a thread is really missing or just dropped from fetch.

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

Asking for an artifact comment thread that is not in the fetched set now says whether the thread genuinely does not exist or whether threads were dropped from the fetch.

Details
  • Raises comments_thread_not_found when the id is absent, with text pointing at the "comments" action as the source of thread ids
  • Raises comments_degraded instead when threads were dropped, so the model does not conclude the thread is gone
  • A filtered listing that comes back empty now tells the model to re-run without thread_id
Evidence

no comment thread ${er} on this artifact \u2014 thread ids come from action "comments"

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

Feedback