{"version":"2.1.273","anchor":"artifact-tool-prefetches-stored-declaration-data-while-readi","canonical_anchor":"artifact-tool-prefetches-stored-declaration-data-while-readi","heading":"Artifact reads handle the stored type declaration more carefully","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/artifact-tool-prefetches-stored-declaration-data-while-readi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Artifact reads handle the stored type declaration more carefully\n\nArtifact reads now skip or prefetch the stored Artifact-type declaration depending on who's reading and what page\n\n**What**\n\nReading an artifact now takes a `storedDeclaration` option that controls whether the stored Artifact-type declaration is included:\n\n- When the page being read is a probed live document or page (and the read isn't specifically for the type page), the stored type declaration is now left out.\n\n- When an owner or writer reads the main artifact page (not a specific file) and the artifact has an Artifact-type declaration, Claude Code now starts fetching that stored declaration at the same time as the main content, instead of waiting until afterward.\n\n**Why**\n\nSkipping the declaration when it isn't needed avoids sending redundant data, and fetching it in parallel for owner\/writer reads hides the extra latency it would otherwise add.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}