{"version":"2.1.275","anchor":"artifact-type-reading-tool-output-now-reports-whether-the-ty","canonical_anchor":"artifact-type-reading-tool-output-now-reports-whether-the-ty","heading":"Artifact type-reading tool output now reports whether the type file was actually read","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/artifact-type-reading-tool-output-now-reports-whether-the-ty","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Artifact type-reading tool output now reports whether the type file was actually read\n\nArtifact type tool output now shows whether the type file was actually read\n\n**What**\n\nWhen Claude Code displays the result of a tool call that reads an artifact's type, it now checks a new `type_file` field in the result. If present, it shows either \"read `<path>` of artifact type\" or \"did not read `<path>` of artifact type\", depending on whether the file was actually read.\n\n**Why**\n\nThis gives a clearer, more honest account of whether the type information came from an actual file read or not.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}