{"version":"2.1.283","anchor":"artifact-read-back-skipped-when-the-write-already-echoed-it","canonical_anchor":"artifact-read-back-skipped-when-the-write-already-echoed-it","heading":"Saving an artifact no longer fetches it again when the save already returned it","tier":"internal","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/artifact-read-back-skipped-when-the-write-already-echoed-it","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Saving an artifact no longer fetches it again when the save already returned it\n\nAfter writing an artifact, Claude Code skips the extra read-back request when the write response already echoed the content\n\n**Unclear.** It is not known which storage backends send the content back with the write, so it is unclear how often the read-back is skipped.\n\n**What**\n\nWhen Claude Code writes an artifact, it can read the artifact back afterwards to confirm the result. It now skips that read-back when the write response says it already sent the content back.\n\n**Why**\n\nThis saves one unnecessary round trip to the server on those writes.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}