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
HomeReleasesv2.1.225entry #7

Claude Code v2.1.225 ·

Artifact comments can be filtered to one thread or resumed with a cursor

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

Use it now Notable New Features
JSON All of v2.1.225
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
New FeaturesKind: in v2.1.225,
What probably matters to youSection of the release
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.

Read from
Names in the bundlethread_idcursorcomments

See this entry in the whole of v2.1.225 →

Feedback