{"version":"2.1.275","anchor":"artifact-read-falls-back-to-reading-it-as-a-frozen-artifact","canonical_anchor":"artifact-read-falls-back-to-reading-it-as-a-frozen-artifact","heading":"artifact read: falls back to reading it as a frozen artifact type link on a 404","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/artifact-read-falls-back-to-reading-it-as-a-frozen-artifact","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### artifact read: falls back to reading it as a frozen artifact type link on a 404\n\nReading an artifact that 404s now falls back to returning its type declaration if it's a frozen artifact type\n\n**What**\n\nWhen reading an artifact page or file returns a 404 (not found) error, Claude Code now checks whether the requested URL actually refers to a 'frozen artifact type' (an entry in a type catalog). If it does, it returns that type's declaration and instructions instead of just reporting the 404 as a failure. This applies to both the page `read` action and the single-file `read_file` action.\n\n**Why**\n\nThis avoids a misleading failure when the URL was never a live artifact page in the first place but a reference to a known artifact type, giving useful information instead of a plain error.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}