Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.309 ·

Artifact creation can now tell the server the user confirmed it

Creating an artifact from a type can now send a create-confirmed flag to the server, with new confirmation constants and an artifact tool list

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

What

Artifacts are pages or documents Claude can create from a predefined type. The function that creates an artifact now takes a createConfirmed argument and passes it on to the create call. When createConfirmed is true, the request also carries a parameter telling the server that the user confirmed the create.

  • The address for creating an artifact from a type is now built from a list of query parameters (extra values added to the end of a web address). It still carries idempotency_key and can now also carry the confirmation parameter. Before, only an optional ?idempotency_key= suffix was built.
  • New constants appear: create_confirmed=1 and anthropic/frameCreateConfirmed.
  • A list of artifact tools appears: pin_artifact, unpin_artifact, publish_version, list_artifacts and list_types.

Why

Artifact creation can now carry an explicit record that a person approved it. Nothing in the members shows a confirmation prompt yet, so this is the request side of a possible confirmation step rather than a visible change.

See this entry in the whole of v2.1.309 →

Feedback