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.225 Home All releases ←olderv2.1.224 v2.1.226newer→
Claude Code v2.1.225

Artifact comment errors distinguish missing thread from degraded fetch

You'll notice
Useful2 Signal0
Artifacts

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

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 →