{"version":"2.1.275","anchor":"artifacts-new-source-restore-read-path-and-artifact-types","canonical_anchor":"artifacts-new-source-restore-read-path-and-artifact-types","heading":"Artifacts: new 'source restore' read path and Artifact Types catalog","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/artifacts-new-source-restore-read-path-and-artifact-types","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Artifacts: new 'source restore' read path and Artifact Types catalog\n\nNew backend support for restoring a published Artifact's source and reading Artifact Types\n\n**What**\n\nA large new module adds the ability to read back the published source of an Artifact (a piece of generated content Claude Code can publish, such as a document or app) through a new `artifact_source_restore` path. It reports detailed reasons when this fails, including permission checks, blocked outbound network access, organization mismatches, read timeouts, version lag, and warnings when another writer has changed the content.\n\nAlongside this, new plumbing supports \"Artifact Types\": reading a type's catalog entry, its instruction file, and the content of individual files within it via `artifact_type_link_read`. This is tied to a feature state called `frozenArtifactTypes`.\n\n**Why**\n\nThis lays groundwork for Claude Code to fetch back and inspect previously published Artifacts and their type definitions, with clearer error messages when that read fails.\n\n- Flag `tengu_cobalt_plinth_moss`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.275; this account: on, anonymous baseline: on, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}