{"version":"2.1.282","anchor":"artifact-persist-failed-guidance-adds-a-case-for-reads-that","canonical_anchor":"artifact-persist-failed-guidance-adds-a-case-for-reads-that","heading":"Artifact recovery guidance now covers re-reads that need your approval","tier":"internal","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/artifact-persist-failed-guidance-adds-a-case-for-reads-that","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Artifact recovery guidance now covers re-reads that need your approval\n\nWhen an artifact's source cannot be shown or saved, Claude is now told a re-read may ask for your approval and not to republish from a partial copy\n\n**What**\n\nSometimes the full source of an artifact cannot be shown inline or saved to disk. Claude Code then tells Claude how to get it back. That guidance changed in two ways:\n\n- A new case covers re-reads that need your approval. Claude is told the re-read will ask you to approve it. It is also told not to republish from a summary, or from a copy marked TRUNCATED or marked as not the exact bytes.\n\n- The existing guidance already warned about TRUNCATED copies. It now also covers copies marked as not the exact bytes.\n\n**Why**\n\nThis makes it less likely that Claude republishes an artifact from incomplete content.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}