{"version":"2.1.248","anchor":"artifact-reads-can-be-served-from-a-local-copy","canonical_anchor":"artifact-reads-can-be-served-from-a-local-copy","heading":"Artifact reads can be served from a local copy","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/artifact-reads-can-be-served-from-a-local-copy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Artifact reads can be served from a local copy\n\nRepeat artifact reads can be served from a local copy instead of a network round trip.\n\n**What**\n\nReading an artifact without naming a version can now be answered from a locally maintained copy of the rendered HTML instead of a round trip to the `*.frame.claudeusercontent.com` host, which makes repeat reads faster.\n\n**Details**\n\n- Only applies when a local copy exists for that artifact; otherwise the remote fetch runs as before.\n- Requests that pin an explicit version always go remote.\n- The read logs the sequence number it was served at.\n\n**Evidence**\n\n`[artifact] read served from the local replica at seq `\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}