{"version":"2.1.309","anchor":"artifact-create-requires-confirmation-flag","canonical_anchor":"artifact-create-from-type-can-send-a-create-confirmed-query","heading":"Artifact creation can now tell the server the user confirmed it","tier":"internal","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/artifact-create-requires-confirmation-flag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Artifact creation can now tell the server the user confirmed it\n\nCreating an artifact from a type can now send a create-confirmed flag to the server, with new confirmation constants and an artifact tool list\n\n**Unclear.** It is not clear whether you will now be asked to confirm before an artifact is created.\n\n**What**\n\nArtifacts 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.\n\n- 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.\n\n- New constants appear: `create_confirmed=1` and `anthropic\/frameCreateConfirmed`.\n\n- A list of artifact tools appears: `pin_artifact`, `unpin_artifact`, `publish_version`, `list_artifacts` and `list_types`.\n\n**Why**\n\nArtifact 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.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}