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 comments can be filtered to one thread or resumed with a cursor

Use it now
Useful4 Signal0
Artifacts Notable

You can read one artifact comment thread by id, or resume a cut-off listing with a cursor.

thread_idcursorcomments
What

The Artifact tool's comments action takes a thread_id to read a single thread and a cursor to continue a listing that was cut off by the size cap. Results echo back thread_filter and cursor so the model knows which view it is looking at.

Details
  • thread_id and cursor are mutually exclusive and both must be lowercase UUIDs, each with its own validation error and error code
  • when a requested thread is not in the result, the model is told to re-run comments without thread_id for the full list
  • truncated listings carry a hint to re-run with cursor, and resumed listings carry a "Resumed from the cursor:" note; threads are listed newest first
  • the tool-use line renders counts such as "read 1 comment thread (filtered)"
  • available to anyone who can use the Artifact tool; neither field existed in 2.1.224
Evidence

` thread_id (read one thread) and cursor (continue the list) cannot be combined — pass one. , thread_filter`

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 →