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
Unclear It is not clear whether you will now be asked to confirm before an artifact is created.
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.
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 you will now be asked to confirm before an artifact is created.