Artifact tool messages now describe actions as unified "list"/"read" with a scope or path instead of separate per-type action names
What
When the consolidated "artifact toolset" is active, tool-result and instruction text for artifact tools is rewritten to use unified action names:
- Old action names like
action "list_assets",action "read_file", andaction "list_files"(used byasset_upload,asset_list,asset_delete,file_list, andfile_read) now appear asaction "list"oraction "read", with ascope(for examplescope: "assets"orscope: "files") or apathargument instead. - Guidance that used to say
action: "describe_type"now saysaction: "read"when this consolidated toolset is active.
Why
Collapsing 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.
tengu_cobalt_plinth_damson Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: off · compiled default in v2.1.265: off
Read once, for one account on one subscription tier, against v2.1.265. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.