{"version":"2.1.265","anchor":"artifact-asset-readlist-tool-use-summaries-drastically-simp","canonical_anchor":"artifact-asset-readlist-tool-use-summaries-drastically-simp","heading":"Artifact asset read\/list tool-use summaries drastically simplified","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/artifact-asset-readlist-tool-use-summaries-drastically-simp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Artifact asset read\/list tool-use summaries drastically simplified\n\nArtifact tool's read\/list-asset summaries were shortened to brief fixed text, dropping detailed approval-scope explanations\n\n**What**\n\nThe short descriptions Claude Code shows for the artifacts tool's `read_asset` and `list_assets` actions (used when displaying what a tool call is about to do) were replaced with two brief, fixed sentences. The previous versions explained in more detail how approval scope worked, including the difference between reading your own artifacts versus others', and coverage of server-side copies.\n\n**Why**\n\nThis simplifies what's shown to the reader when these actions run, though it means less detail is surfaced about exactly what access is being used.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}