{"version":"2.1.292","anchor":"artifact-asset-and-file-reads-try-the-artifact-service-first","canonical_anchor":"artifact-asset-and-file-reads-try-the-artifact-service-first","heading":"Artifact files are fetched from the artifact service first","tier":"internal","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/artifact-asset-and-file-reads-try-the-artifact-service-first","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Artifact files are fetched from the artifact service first\n\nWhen fetching an artifact's assets or files, Claude Code now tries the artifact service first when it has a token\n\n**What**\n\nWhen Claude Code fetches the files or assets of an artifact, it now first tries the artifact service if it has a sign-in token available. Before, it went straight to the content host, or to a relay for public artifacts.\n\nError messages now say which one answered: \"artifact service\" or \"content host\".\n\n**Why**\n\nThe network route for artifact files has changed, which matters if you need to know where those requests go or are reading an error about them.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}