{"version":"2.1.257","anchor":"new-artifact-tool-version-action","canonical_anchor":"new-artifact-tool-version-action","heading":"New Artifact tool \"version\" action","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/new-artifact-tool-version-action","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### New Artifact tool \"version\" action\n\nThe artifact tool gains a version action that resolves and records an artifact's version, re-checking the approved target first.\n\nThe artifact tool gains a `version` action that runs a dedicated version-resolution flow with retry progress reporting and updates the artifact's read-version state afterward; it's rejected if the live-doc module isn't available in the build, and re-validates the approved action and URL still match before running, guarding against a changed target between approval and execution. `getToolUseSummary` and the auto-classifier describe `version` as versioning an artifact with nothing uploaded.\n\nAlongside `version`, a new `open` action lets Claude show an existing artifact read-only, distinct from list\/publish, and is treated as read-only by the classification logic. New `get_handlers`, `call_handler`, and `run_script` actions add server-callable handler support, gated by boolean flags in the tool constructor and an ACTION description clause added to the schema when handlers are enabled; `get_handlers` is classified read-only, while `call_handler`\/`run_script` are treated as writes unless a handlers-action-write check says otherwise. These gates are logged in the schema-build telemetry line and folded into the action enum.\n\n- Area: Artifacts\n- Names: `version`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5"}