Claude Code v2.1.225 ·
Artifact tool parses an optional cursor argument
The artifact tool now accepts a cursor value, groundwork for fetching comments page by page.
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.225,
In DevelopmentSection of the release
A cursor argument is parsed but nothing in this build sends or consumes it.
What
The artifact tool's argument extractor now reads an optional string cursor in addition to thread_id and text.
Details
cursor is returned as part of the parsed argument shape- no schema entry or request consuming it was found in this build, so it appears to be plumbing ahead of paginated comment fetching
Evidence
"cursor" in e
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 →
