{"version":"2.1.265","anchor":"new-artifact-type-instruction-wording-toggle-tied-to-the-ar","canonical_anchor":"artifact-tool-actions-being-consolidated-into-listread-with","heading":"Artifact tool actions consolidated into list\/read with a scope","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-artifact-type-instruction-wording-toggle-tied-to-the-ar","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Artifact tool actions consolidated into list\/read with a scope\n\nArtifact tool messages now describe actions as unified \"list\"\/\"read\" with a scope or path instead of separate per-type action names\n\n**What**\n\nWhen the consolidated \"artifact toolset\" is active, tool-result and instruction text for artifact tools is rewritten to use unified action names:\n\n- Old action names like `action \"list_assets\"`, `action \"read_file\"`, and `action \"list_files\"` (used by `asset_upload`, `asset_list`, `asset_delete`, `file_list`, and `file_read`) now appear as `action \"list\"` or `action \"read\"`, with a `scope` (for example `scope: \"assets\"` or `scope: \"files\"`) or a `path` argument instead.\n\n- Guidance that used to say `action: \"describe_type\"` now says `action: \"read\"` when this consolidated toolset is active.\n\n**Why**\n\nCollapsing several type-specific action names into a common `list`\/`read` pair with a `scope` or `path` makes the artifact tool's interface simpler and more consistent for anything that reads or lists artifact content.\n\n- Flag `tengu_cobalt_plinth_damson`: Not enough to say (read for one account on one subscription tier against v2.1.265; this account: no value returned, anonymous baseline: off, compiled default: off)\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5"}