{"version":"2.1.268","anchor":"artifact-tool-list-filesread-file-now-resolve-and-return-a","canonical_anchor":"artifact-tool-list-filesread-file-now-resolve-and-return-a","heading":"Artifact tool: list_files\/read_file now resolve and return a type object for type-locked files","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/artifact-tool-list-filesread-file-now-resolve-and-return-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Artifact tool: list_files\/read_file now resolve and return a `type` object for type-locked files\n\nArtifact file listing and reading now include the artifact's declared type when the file is type-locked\n\n**What**\n\nWhen the artifact tool's `list_files` and `read_file` actions handle a file that is \"type-locked\" (tied to a specific artifact type), Claude Code now looks up that type's metadata and includes it as a `type` field in the response, alongside the existing `from_type` flag. The `read` action also now records `type_named` in its internal telemetry when the artifact has a title.\n\n**Why**\n\nThis gives Claude Code more context about what kind of artifact a file belongs to when listing or reading it, which can help produce more accurate handling of type-specific files.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}