Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.317entry #378

Claude Code v2.1.317 ·

Artifact listing can page through results, and tool results say which built-in tool ran

Listing artifacts now accepts page_token to fetch the next page, and tool-result details gain an optional built_in_tool field

Under the hood Internal Changes
JSON All of v2.1.317
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SDKArea: what it touches
Internal ChangesKind: in v2.1.317,
Internal ChangesSection of the release

Unclear It is not clear whether the tool actually accepts page_token yet, or only its description mentions it.

What

Several parts of the data Claude Code exchanges with programs that embed it changed:

  • Tool-result details gained an optional built_in_tool field.
  • The artifacts tool's list action accepts page_token, the next_page_token an earlier listing of the same scope gave, to list the artifacts after it. Only limit, scope and page_token may go with a list request.
  • The description of server_display_name was reworded.
  • A configuration format gained fields about the program's use case.
Why

Programs embedding Claude Code get more detailed information back, and long lists of artifacts can be read a page at a time.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear whether the tool actually accepts page_token yet, or only its description mentions it.

See this entry in the whole of v2.1.317 →

Feedback