Repeat artifact reads can be served from a local copy instead of a network round trip.
What's wrong with this entry?
Reading 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.
- Only applies when a local copy exists for that artifact; otherwise the remote fetch runs as before.
- Requests that pin an explicit version always go remote.
- The read logs the sequence number it was served at.
[artifact] read served from the local replica at seq
Strings lifted out of the shipped bundle, so the claim above can be checked against them.